I have been looking at the Jacob engine, BPEL runtime and BOM and feel comfortable with the implementations. I would be fine with moving these into the trunk. I would like to talk more about the build and get a better understanding about project dependancies.
Actually if it's ok for everybody, I'd also move the dependencies of these modules, so that we can at least have something that compiles and run a couple of examples. Then we can start from that and start "breaking" things to comply with the specs we already have (like deployment and content API) and the ones we still have to write :) Otherwise nothing will compile and we won't be to run any single thing. So that would mean the following modules: - Axis2 (IAPI implementation for Axis2) - BPEL API (mostly DAO interfaces, IAPI interfaces, events, management API) - BOM - Compiler - DD (deployment descriptors) - XPath 1.0 and 2.0 support. - Bpel-Obj (already in) - Bpel-Parser (already in) - Bpel-QL (query language for retrieving instances information, needed by management API). - Bpel runtime - Bpel sechdule (quartz) - Bpel schemas - DAO-* - Examples - Jacob - JBI - Minerva (connection pool) - Utils (already in) That will give us a working basis to start removing the dependencies we don't like, changing the things that don't comply to specs and so on. But I'd find much more comfortable to start from something that builds and runs. If you like I can then write something about build (actually nothing special, only using Maven2) and dependencies. What do you think? Cheers, Matthieu
