Christopher Oliver wrote:

If you ask me, this is mainly a semantic problem, not a technical one.

If a template is not called from a (Javascript) flowscript, there is no FOM, and therefore no FOM variables are available in JXTG. For the case where it _is_ called from a flowscript, then the FOM is and IMO should be accessible.

The request, session, etc, variables that are described as deprecated are unnecessary and inappropriate when the template is called from the flowscript (since they provide no additional information beyond the FOM, but yet have an "impedance mismatch" with the flowscript model). They are simply carried over from the original (pre-FOM) implementation for backward compatibility.

Thanks for clarifying. IMO we should just remove the pre-FOM stuff from the refactored JXTG, we cannot support deprecated things for ever.


As I stated in the original thread about this, if someone feels that it is appropriate to call JXTG from some other context then they need to define the model that makes sense in that context and document it.

Yes, we should do it like this instead. IMO we need to make a non flow FOM subset available, so that JXTG can be used without flow for simple cases where one just need access to request params etc. This should in turn, be done by factoring out the relevant parts of the FOM code. For the time being I think we should focus on the refactoring of _existing_ JXTG functionality, we can add the possiblility to use JXTG in other sontexts later.


As far as the technical problem, the variable context provided to the template needs to be made configurable (in the case where it is called from a flowscript the configuration would match the current behavior). In the case where it is called from another context then a suitable configuration for that context can be provided.

However, I think you should discuss the details of some specific use cases of using JXTG without flowscript (for example JavaFlow - what exactly is its model?), before attempting to implement configurable variable contexts for JXTG.

Yes.

Hope this helps and regards,

It helps, thank you.

/Daniel



Reply via email to