[
https://issues.apache.org/jira/browse/TUSCANY-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TUSCANY-1365.
--------------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-Next
Patch applied under revision #550339
The implementation.bpel was also removed from build as it now needs ODE to be
built locally first.
> Bootstrap the ODE server in the BPEL implementation
> ---------------------------------------------------
>
> Key: TUSCANY-1365
> URL: https://issues.apache.org/jira/browse/TUSCANY-1365
> Project: Tuscany
> Issue Type: New Feature
> Components: Java SCA BPEL Implementation Extension
> Reporter: Matthieu Riou
> Fix For: Java-SCA-Next
>
> Attachments: ode-init.patch, ode-init.zip
>
>
> I'm attaching a patch and a zip (for new files) containing the necessary code
> to bootstrap the ODE BPEL server. It actually doesn't give you much as it's
> just initializing all resources needed by the server and then loading it, so
> nothing is there for exchanging messages. But it's already a start.
> Testing is a bit rough as it's still very preliminary but here are the steps
> to get the test case to run:
> 1. You'll need to build ODE locally first. I'm basing the code on ODE's trunk
> as some tweaks or improvements here and there will probably be needed in ODE
> as well. Later on, when the implementation is bit more stable, I'll publish
> snapshots and eventually transition to an ODE release. In the meantime, here
> is how to build ODE (using buildr):
> http://incubator.apache.org/ode/jacob.html
> Run the "install" task instead of "package" to have the created jars
> published in your local directory.
> 2. The server initializes Derby, so you need to have a Derby database. For
> now it will be looking for it in an ode-work subdirectory of the BPEL
> implementation root directory (until we implement a better way to find it).
> Create this directory and copy the jpadb directory found in
> ode/dao-jpa-ojpa-derby/target/derby after ODE has been built in it. You
> should end up with implementation-bpel/ode-work/jpadb.
> 3. Run "mvn test". Maven2 being a pain, it will download the whole world.
> Several things aren't actually required but come with transitive
> dependencies, we'll have to exclude things at some point but for now it
> should work.
> If the Maven2 build fails because it couldn't download a dependency, you'll
> need to add some remote repositories. Here are the ones we have in ODE:
> repositories.remote << "http://pxe.intalio.org/public/maven2";
> repositories.remote <<
> "http://people.apache.org/repo/m2-incubating-repository";
> repositories.remote << "http://repo1.maven.org/maven2";
> repositories.remote << "http://people.apache.org/repo/m2-snapshot-repository";
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
