Daniel Fagerstrom wrote:<snip/>
In a next step the cache object should be factored out from the ExecutionContext and replaced by some kind of script manager, so that we can have the code that compiles and caches the scripts at one place.
Then execute takes a number of events as arguments, I would like to abstact the coupling between execution and event implementation, but how it should be done requires more thinking.
I think the approach Jonas introduced could be used. Still it needs some extra features (like jx:parameter or jx:evalBody handling). We need a lot of regression tests to do that right I suppose.
Jonas prototype only handles part of it. The setup should occur at compile time and also we must decide how the tag code should be allowed to access the body of the content of the XML representation of the tag.
Each tag has code in three places: its start tag that contains data, in the parser for setting it up and inexecute for executing it. That is rather confusing, so we shoud put all the three parts in one class. How this can be done has been discussed in the above thread among other places.
Hiding the jxpath and jexl specifc code beyond one interface would also be nice.
There is JXTExpression class. If we are not planning to implement pluggable ELs the only thing we have to do is to create JXTContext that would join jextContext and jxpathContext.
We are planning to implement pluggable ELs, but we don't need to do that in the first step.
/Daniel
