Thanks. I think I understand the JBI related directory structure now...
ode/distro-jbi --> jbi examples (assembles full jbi installer package from ode/jbi) ode/jbi --> builds ode for a jbi architecture (as opposed to axis) ode/jbi-examples --> former home of jbi examples. no longer used ode/jbi-install --> no longer exists If this is correct then I am happy to update the jbi deployment documentation ( http://incubator.apache.org/ode/jbi-deployment.html ) with current directory and variable names. This should be something like ... 1) No change 2) No change 3) (from ode directory) cd jbi mvn install 3.5) (from ode directory) cd distro-jbi mvn install 4) (from distro-jbi directory) cp target/distro-jbi-2.0-SNAPSHOT.zip SERVICEMIX_DIR/install and so on... --Dan On 3/14/07, Alex Boisvert <[EMAIL PROTECTED]> wrote:
ODE_HOME should point to where you have extracted the distro-jbi-2.0.x.zip . This zip contains all scripts to build and test the examples. alex On 3/14/07, Dan <[EMAIL PROTECTED]> wrote: > > Hi, > I have built and deployed Ode onto ServiceMix. > I am now trying to assemble and install the PingPong example. Building > seems to work fine. When I try to create the assembly by calling ant from > the PingPong directory it fails when validating ODE_HOME. > I'm not completely sure what ODE_HOME should be set to. Right now I have > it > pointed to the JBI build target. > > [PingPong]$ ant > Buildfile: build.xml > ... > validate-ode-home: > > fail-invalid-ode-home: > > BUILD FAILED > /opt/ode/distro-jbi/target/stage/examples/base.xml:82: Invalid property ' > ode.home'=/opt/ode/jbi/target/ode-jbi-2.0-SNAPSHOT-installer > > Total time: 0 seconds > > [PingPong]$ find /opt/ode -name ode-bpel-compiler.jar > [PingPong]$ find /opt/ode -name ode-bpel-compiler* > /opt/ode/jbi/target/ode-jbi-2.0-SNAPSHOT-installer/lib/ode- > bpel-compiler-2.0-SNAPSHOT.jar > > Thanks, > Dan >
