[
https://issues.apache.org/jira/browse/COCOON-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526579
]
Grzegorz Kossakowski commented on COCOON-1816:
----------------------------------------------
Yes, I think that this has been fixed in refactored template
generator/transformer. Use "newjx" generator in your sitemaps in order to
utilize refactored code.
> JEXL Does not support full cocoon object model on its own
> ---------------------------------------------------------
>
> Key: COCOON-1816
> URL: https://issues.apache.org/jira/browse/COCOON-1816
> Project: Cocoon
> Issue Type: Bug
> Components: Blocks: Templating
> Affects Versions: 2.1.8
> Reporter: Berin Loritsch
> Priority: Critical
>
> JEXL will not allow you to access cocoon.request or cocoon.session and
> company unless a flowscript performs a sendPage related request. This
> violates the principle of least surprise, and caused over four hours of
> productivity loss just trying to figure out why something that _should_ work
> wasn't. All the documentation suggests that I could access the full cocoon
> object model without any reference to flowscript.
> The cocoon object model should be set up in a way where it is accessible
> directly in JEXL as well as in the flowscript. In short, it should be set up
> properly as a core feature so that it is accessible and usable in a
> consistent way throughout the entire application. JEXL, Flowscript, or any
> other new technology that comes along. One component should not depend on
> another to set things up if you can't reasonably expect them to be completely
> coupled. In short, JEXL should be usable independantly from Flowscript.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
