BURGHARD Éric wrote:
Daniel Fagerstrom wrote:
Instruction Access ==================
What objects should instructions and macros be able to access? Curently for the needs of the JXTG instructions, the instructions has access to a ExpressionContext that contains the FOM "view" that is available in expressions in JXTG. They also have access to an ExecutionContext that currently contains a script manager and a map with macros, we might need a SourceResolver also. There are also some other stuff that not are relevant for the current discussion.
The questions are:
* Should the ExecutionContext also contain a ServiceManager?
* Should the ExpressionContext also contain a ServiceManager? (makes the ServiceManager available in expressions)
IMO the ExecutionContext should have access to the ServiceManager and the ExpressionContext shouldn't. WDYT?
Both the above question might be suitable for votes, but I think they need more discussion about them before we do that.
-1 if we can pass dom (perhaps bean too) with pipeline parameter (see my answer to stefano). +1 otherwise.
What about starting defining a functionnal macros API, so that cforms could
plug properly in jx ?
I'm more interested in making cforms more template friendly.
/Daniel
