AnsweredAssumed Answered

pvm will be moved into engine

Question asked by tombaeyens on Oct 21, 2010
Latest reply on Oct 25, 2010 by tombaeyens
after some reflection and seeing the disadvantages of extracting pvm as a separate module, we came to the conclusion that pvm should be merged into the engine.

in the future, the interpretation algorithm should work against interfaces (instead of the impl objects).  that way we can build separate runtime execution datamodels for the different strategies like pojo usage, DB persistent usage (with lazy loading) and later also a cloud based runtime execution model.

the plan is that next week i'll merge pvm into the engine module.  after that we can still work further towards those long term goals without impacting the api.

also the separate juel module will be merged into the engine module.

Outcomes