Cool - I was just digging through the RmiTransportServerImpl trying to get my head around that :)
As for the JBI plugin I was really thinking more for the creation of your component installer - since if you create the install using the JBI plugin then that adds a little magic for people who want to use Maven to create their SU - so example they only need to add a dep to the component project and the tooling will work out the name of the service engine and also if they reference that SU in an SA as a dep it will automatically create the jbi.xml for all parties. Just a thought - currently I'm trying to get the ODE SE run deploy through Eclipse onto ServiceMix and then editing the BPEL process using the new Eclipse BPEL project - so it would be nice to have an archetype for the Service Unit (much like that seen in the ServiceMix project for our components). P On 9/8/06, Alex Boisvert <[EMAIL PROTECTED]> wrote:
Hi Philip, The exception you're getting is inoffensive and Ode should work regardless. We need to rework the JNDI/RMI integration a little... Ode currently uses its own context -- a legacy from the standalone PXE distribution. As for the JBI plugin, I've considered it seriously but in the end came back to Ant for simplicity. My goal was to put the examples in the distribution, including the scripts to rebuild the example such that users can modify the BPEL/WSDL files, run the scripts and easily redeploy. I was a little afraid to push Maven unto the end-users because of its non-determinism. Many users have Ant already installed but only a few have Maven2 installed. An option would be to bundle both Maven2 projects (using the JBI plugin) and Ant build scripts and leave it to the users to use whichever they are most comfortable with... alex Philip Dodds wrote: > Thanks for all the help so far - basically I'm just trying to get the ODE > JBI SE running against the ServiceMix 3.0 release so that we can start > looking at BPEL2 support :) > > I am getting a little further - though I got a little confused by this > error: > > java.rmi.ServerException: RemoteException occurred in server thread; > nested > exception is: > java.rmi.UnmarshalException: error unmarshalling arguments; nested > exception is: > java.lang.ClassNotFoundException: > org.apache.ode.ra.transports.rmi.OdeRemote (no security manager: RMI > class > loader disabled) > at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java > :385) > at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java :240) > at sun.rmi.transport.Transport$1.run(Transport.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at sun.rmi.transport.Transport.serviceCall(Transport.java:149) > at sun.rmi.transport.tcp.TCPTransport.handleMessages( TCPTransport.java > :466) > at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run( > TCPTransport.java:707) > at java.lang.Thread.run(Thread.java:595) > at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer( > StreamRemoteCall.java:247) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java > :223) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343) > at sun.rmi.registry.RegistryImpl_Stub.rebind(Unknown Source) > at org.apache.ode.jca.server.rmi.RmiTransportServerImpl.start( > RmiTransportServerImpl.java:91) > at org.apache.ode.bpel.connector.BpelServerConnector.start( > BpelServerConnector.java:44) > at > org.apache.ode.jbi.OdeLifeCycle.initConnector(OdeLifeCycle.java:330) > at org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:130) > at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init( > ComponentMBeanImpl.java:196) > at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart( > ComponentMBeanImpl.java:283) > at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start( > ComponentMBeanImpl.java:212) > at org.apache.servicemix.jbi.framework.InstallationService.install( > InstallationService.java:325) > at > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive( > AutoDeploymentService.java:247) > at org.apache.servicemix.jbi.framework.AutoDeploymentService$2.run( > AutoDeploymentService.java:592) > > > Also I was wondering whether ODE had considering using the ServiceMix JBI > plugin which can do a lot of the packaging steps that are currently being > done by the Maven assembly plugin - it can also do some clever stuff > in the > JBI space around creating Service Assemblies and Service Units? > > Cheers > > Philip >
