I am attempting to install the Glassfish (Open JBI Components) SOAP binding component (http://wiki.open-esb.java.net/Wiki.jsp?page=HTTPBC) into Servicemix 4. The reason for this is to be able (hopefully) to leverage the Glassfish Metro implementation of JAX-WS, which includes much more current versions of some of the WS-* standards (in particular, WS-RM) than CXF does. (Please validate my understanding here, if you would...I would much rather use CXF but I need WS-RM 1.1 support...) When I follow the instructions at http://wiki.open-esb.java.net/Wiki.jsp?page=JavaSEIncubator and http://wiki.open-esb.java.net/Wiki.jsp?page=JBossIncubator (where the Open JBI folks have apparently demonstrated the ability to deploy the BC in other JBI containers), I run into the problem described at https://issues.apache.org/activemq/browse/SMX4NMR-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60879#action_60879 (it seems that the BC does not strictly follow the JBI spec, and so when SMX inits and installs the BC we get exceptions about Context access...) So I grabbed the code for the BC, removed the non-compliant code, built it, and now I can install it into SMX without any errors showing up in the log. When I do an osgi:list, I see it appear (state=Active). When I do a jbi:list, the BC shows up, but its state is "Unknown" (same as servicemix-http, servicemix-jms, and servicemix-wsn2005). What does this "unknown" state mean? Is there an easy way to test if the BC is fully ready to accept messages on its external protocol and pass them on to the NMR? Has anyone else on the list successfully deployed the Open JBI HTTPBC into servicemix 4? Thanks for your help. --Scott
