http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=106971256203925&w=2 http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106140130601357&w=2 http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106140404404983&w=2
Regards,
Chris
Antonio Gallardo wrote:
Hi Christopher:
I am relly newbie in JXTemplate. We currently, does not see a needs for this. Can you provide some examples, where it is needed?
We use flow and when needed we send the requiered data of the mentioned properties from flow.
I think this allow us to have a clean separation of concerns.
I will be glad if you can show a sample where you need this. Please note, I am not telling: "you are wrong". I am sure you have more experiences in the field. We are aware of that. :-D
Best Regards,
Antonio Gallardo
Christopher Oliver dijo:
I'd like to change JXTemplate to use a subset of the FOM, namely by providing a variable "cocoon" with the following properties:
- request - session - context - continuation
Each of these would be a reference to the corresponding FOM object. This will unify the object model of the controller and view.
I will deprecate the existing "request", "response", "session", "context" (which point at org.apache.cocoon.environment Java objects) and "continuation" variables but continue to support them.
Any objections?
