JMS Transport

[jgilbert]

Has anyone written or are there plans to write a JMS transport for jboss remoting?

My scenario is that I would like to use a jms transport behind a oneway web service operation.

[tom.elrod]

No plans for JMS transport within remoting.

[jgilbert]

Do you think this is something reasonable that I should take a stab at or is there a better approach?

[tom.elrod]

You're welcome to add a JMS based transport. The reason it really never showed up on our radar was because felt it would be difficult to expose the full power of JMS through remoting API (i.e. durable topics, persisted messages, message acknowlegement, etc.). We figured if someone needed to use JMS, would be best to use an JMS implementation directly.

[jgilbert]

Makes sense.

I am just trying to reproduce the kind of capability with jbossws that i could do with the axis jms transport.

[tom.elrod]

Don't know the axis jms transport that well. What is the advantage of using that over http?

[jgilbert]

Reliability. My scenario is a Oneway asynchronous soap message. So, jbossws makes the request and moves on without waiting for a response. I then want jboss messaging to ensure the message gets to the otherside. So far it is working good. I created a straight forward JmsClientInvoker.

Now I am working through the jbossws mdb support on the otherside: http://labs.jboss.com/portal/jbossws/user-guide/en/html/jms-transport.html

[tom.elrod]

Ahh, for one way can see why would be important.

Great that you are making progress on a transport. Let me know if any remoting specifics I could help with.