[ 
https://issues.apache.org/jira/browse/LABS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643568#action_12643568
 ] 

Simone Gianni commented on LABS-193:
------------------------------------

This has been done, but care should be taken when writing documentation.

Basic explanation :
- This is an egg-chicken problem, cause main content drives which template to 
use, and the template decides if a content is a main or not.
- Anyway, is not an unresolvable one.
- Every time a request arrives, Magma can choose between three template:
 - The one an aspect explicitly assigned
 - The one that was used in the previous request
 - The default one
- If there is an explicitly assigned one, use that, cause the programmer is 
always right :)
- If there is a previous one, ask that one if the current request should be 
considered a main or not
 - Note that this does not imply to execute all the formatting, but only to 
resolve producers
 - When cglib (see LABS-221) will be in place this will not even mean calling 
the methods
- If it is a main, then revert to the default template
- If this is not a main, then reuse the previous template

Placing it simpler, it means that the previous template will only be used if it 
is able to handle the request as an auxiliray content, otherwise either a 
specific one is specified, or the default one will be used.



> WEB: reuse last template by default
> -----------------------------------
>
>                 Key: LABS-193
>                 URL: https://issues.apache.org/jira/browse/LABS-193
>             Project: Labs
>          Issue Type: Bug
>          Components: Magma
>    Affects Versions: Current
>            Reporter: Simone Gianni
>            Assignee: Simone Gianni
>             Fix For: Current
>
>
> If a producer has no specified template, then the template from the previous 
> request should be used. The previous template can be stores statefully on the 
> session, or statelessly as a cookie on the client.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to