project_key: SOA Both HornetQ and JBM client libraries are supposed to be present in the client directory but the JBM client library is removed after switching to HornetQ. This is inherited from EAP.
Link: Added: This issue depends JBPAPP-5041
Martin, JBPAPP-5041 has been redefined. Can you check if it would cause any issues on the SOA side?
Thanks Rajesh, I updated the issue.
This was triaged for SOA 5.1.0. Not in SOA 5.1.0
Link: Added: This issue relates to SOA-3228
HornetQ will be reintroduced.
It doesn't make sense to have the JBoss Messaging client libs available when the default messaging provider is HornetQ. If a user wants to use a JBM client (that would be talking to a remote JBM server anyway) they would add the JBM client libs to the application itself, however this is unlikely.
Maybe putting them in a separate "extras" folder or renaming them?
For ESB at least, jboss-messaging-client.jar seems to be a required JAR for a remote service invoker invocation against a SOA-P server using jboss-messaging. Even if you are running hornetq locally, you may want to invoke a service on another SOA-P server.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: There is a problem when using HornetQ with the JBoss Messaging Client. The client's libraries are not transferred over after the user has switched to HornetQ. As a result, users cannot access these libraries in HornetQ. To work around this, users should add the JBM client libraries to the application itself.