I have the same problem and cannot find an answer. There has to be a way.
There are some scenarios which are explained for connectivity to the WebsphereMQ and similar can be tried/looked with weblogic stuff.
The simplest one is to push the messages from the weblogic messaging to Jboss Messaging queue , the Jboss Messaging Queue will have the MDB listening to the messages which come from weblogic messaging system
The similar scenario is explained over here
Some more info can be obtained from here
We now have the WebLogic topic messages being sent to a secured queue (one of the default queues, queue/A) on our JBoss server. However, we haven't been able to configure our EJB3 MDBs to listen to the local queue. It should be an easy thing but has turned out to be anything but. We are getting a "not bound" exception when JBoss tries to deploy the MDB to listen to queue/A.
Any tips on what the solution might be? Here are the activation configs we are using in our MDB:
You don't need to set the provider URL if you're connecting locally. I'm pretty sure that providerUrl and JmsProviderAdapterJNDI aren't needed.