Vadim Gritsenko wrote:
...
First we are creating blocks for more modular design and the next thing is we are coupling everything back into monolith. I feel that's not the right way to go.
We've got more than 5Mb worth of optional JARs (not counting blocks' libs) and if you think one of them -- like jxpath -- belongs to the core than we better poll opinions of all devs here and move it there.
I think that is a problem whose scope is much broader than VelocityGenerator,
Yep.
and I don't think it's appropriate to use that as an excuse for -1-ing the integration of the Velocity generator with the flow layer. For what it's worth, the current flowscript implementation already uses JXPath and Rhino, so no new dependencies are really being introduced by VelocityGenerator.
Hm. Are you saying that flow is hardwired to JXPath? /me searching... Right. That's true.
Ok; I'm +0 then on replacing VelocityGenerator with FlowVelocityGenerator, and I propose we move jxpath into the core. Unless somebody comes up with a flow without jxpath.
Vadim
