WEDIA WMS front engine

WEDIA WMS front engine

Posted on Thursday, November 05, 2009

  • | Facebook
  • Twitter
  • Delicious
  • print

A large spider web structure for an easy and understandable use. Discover structure and concepts.

Section(s): front office, templates, XMS engine

The hierarchy of JSPs for building a front page is fully defined in the application WAR. It defines a specific schema of JSP inclusions based on actions and the capacities of the noheto:include tag.
However, WMS adds an over concept of template-based-objects-view pages and allows the development of different websites with different skins within the same data model.

Check  Previous readings

apply  Read also

Default Engine

The WebApp war implements 3 defaults entry points representing 3 basics actions  :

  • view : will load the object asked in parameters and draw it.
  • search : load every tools you need to make a lucene / or what-ever-you-want search. Is able to load an active object if asked.
  • index (wich includes the action homepage ) : sometimes, a home page does not correspond to a simple view of an object, this action lets you draw an entire page with what you want.

Each one these three actions are declared in the SAN folder by :

  • a root action-named jsp like /view.jsp to call them easily
  • an action-named folder in [SAN]/front like [SAN]/front/view 

These action-named folders includes also a proper structure of inclusions shared between a common part (headers, navigation, footer ) and a specific part.



Also, these sections implement there own hirarchy of JSPs who will built an html structure.
Finally, the only JSPs who should have to implements are the JSPs with a _content suffix.

Example : /front/view/content.jsp hierarchy

detail_actions_content.jsp : schould draw blocks or links actions related 
to the current content like print or next article. As detail_actions.jsp draw the html container zone, 
only your content is needed.
 
details_element_content.jsp : draw a zone containing all informations about your current object.
For example, this is where you have to draw the content of a news or an article.
 
details_element_content_list_item.jsp : this JSP has the particularity to never be called directly by the engine. 
It have to be used to draw an element in a list.
For example, a category draws a list of news. In the tag noheto:objectList you will write :
   
  <noheto:objectsList objectname="news" where="parentcategory = ${currentCategory.identity}" scope="request">
    <noheto:include page="/front/view/content/details/details_element_content_list_item.jspz?form_object=news" />
  </noheto:objectsList>
 
 With the tag noheto:include, you will draw a list of news represented in a list. And the template's JSP for it 
will be in the [san]/objects/news/front folder
 
sidebar_content.jsp : represents the linked contents of the current object. 
It corresponds to the usual blocks we found on the lateral zone of a page web like read also or the tag cloud

From the back-office, you may want to make a preview of an object before publication so we created a fourth action  :

  • preview :  This action will override the overs and initialize tools to previsualize them without any intrusives modifications of the common view. 

We provide an implementation of a preview system with WMS but a the developper can change it if it does not correspond with its need.