If you used the jbi-component archetype then you probably need an xbean.xml - since your deployer is extending AbstractXBeanDeployer.
You might want to look at http://devzone.logicblaze.com/site/how-tos.data/ServiceEngine.swf While this shows the open source tooling for FUSE it in fact leverages the same archetypes - ie. servicemix-service-engine and servicemix-service-unit (they are simply built into the Eclipse tooling) - it shows the archetype creating a project and then the service unit and service assembly projects being created. P On 9/12/06, jhair <[EMAIL PROTECTED]> wrote:
I must be missing something. I used the plugin to create the jbi-component, the SU, & SA. I specified the jbi-component dependency in the SU pom.xml and created a servicemix.xml. When the SU is packaged into the SA and deployed, I get the error "Unable to find suitable deployer for Service Unit". Are you saying that the contents of my SU should either include an xbean.xml (defining the endpoints) or a servicemix.xml? I used a servicemix.xml but should have used xbean.xml due to creating the jbi-component using the maven2 jbi-plugin archetype:create. Does the jbi-plugin create 2 different JBI components? One that uses xbean.xml and another that uses/requires servicemix.xml? Thanx, jsh gnodet wrote: > > SU packaging is specific to each component, so if you create your own > component, the content of the SU will be specific to it. > Components created using servicemix-common may register > an XBeanDeployer on the ServiceUnitManager. In such a case, it will > accept (by default) a file named xbean.xml, which should contain > endpoints definitions for the component. > > When you create an SU using the maven2 plugin, you need to add > a dependency on your component inside the pom.xml. It will be > used by the tooling when packaging the SA to specify the target > component for this SU. > > On 9/11/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote: >> >> The servicemix.xml configuration file for the lightweight container >> must contain the >> <sm:serviceunit id='jbi'> >> tag, with activationSpecs inside it. >> Given your configuration, this is the only error I can think about. >> >> >> On 9/11/06, jhair <[EMAIL PROTECTED]> wrote: >> > >> > >> > I'm having problems deploying/installing JBI artifacts to service mix. >> > >> > Using 3.0-M2-incubating, I've created a jbi-component, service-unit, >> and >> > service-assembly modules using maven2 archetypes. I added >> servicemix.xmlto >> > the service-unit, and specified the service unit as a dependency for >> the >> > service assembly. After starting servicemix with conf/servicemix.xml, I >> > copy >> > the jbi-component ZIP into SM's install directory and the log files >> show >> > it >> > deploys without errors. However, when I try to copy the service >> assembly >> > into the deploy directory, SM complains with the following error: >> > >> > Unable to find suitable deployer for Service Unit >> > >> > My service-unit zip contains the following: >> > lib >> > servicemix-components-3.0-incubating-SNAPSHOT.jar >> > META-INF >> > jbi.xml >> > servicemix.xml >> > >> > My service assembly contains the following: >> > META-INF >> > jbi.xml >> > sample-su.zip >> > >> > Can someone point me to where I've messed up? Is there more information >> > that >> > I need/should provide? >> > >> > Thanx, >> > jsh >> > -- >> > View this message in context: >> > >> http://www.nabble.com/Deploying-JBI-component-created-using-maven2-tf2249832.html#a6239963 >> > Sent from the ServiceMix - User forum at Nabble.com. >> > >> > >> >> >> -- >> Cheers, >> Guillaume Nodet >> > > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Deploying-JBI-component-created-using-maven2-tf2249832.html#a6277631 Sent from the ServiceMix - User forum at Nabble.com.
