My apologies for posting to wrong forum... its was 02:30am, and I was a little tired. :-)
Thanks for your post and the info on the seperate SUs. I have done this and made the change to the jbi.xml file as below. Using MC4J console I can see the service assembly registered, but no service units. This is what I am assuming is the heart of why I am not seeing my JMS queue or Bean component.... the SUs are seemingly not registering any of their contents. The log for ServiceMix definitely shows a "Finished installation of archive: CatalogService.zip" message by the AutoDeploymentService on the log. Is it possible for the SA to register, and the SUs not to? And any ideas as to why both SUs are not registering? Kind regards, Jason ------------ <?xml version="1.0" encoding="UTF-8"?> <jbi xmlns="http://java.sun.com/xml/ns/jbi"; version="1.0"> <service-assembly> <identification> <name>catalogService</name> <description>CatalogService Service Assembly</description> </identification> <service-units> <service-unit> <identification> <name>catalogBeanService</name> <description>CatalogService Service Unit</description> </identification> <target> <artifacts-zip>catalogservice-su.zip</artifacts-zip> <component-name>servicemix-beancontainer</component-name> </target> </service-unit> <service-unit> <identification> <name>catalogJMSService</name> <description>CatalogService JMS Service Unit</description> </identification> <target> <artifacts-zip>catalogservice-jms-su.zip</artifacts-zip> <component-name>servicemix-jms</component-name> </target> </service-unit> </service-units> </service-assembly> </jbi> -- View this message in context: http://www.nabble.com/Usage-of-lightweight-components--tf3325766s12049.html#a11759261 Sent from the ServiceMix - User mailing list archive at Nabble.com.
