-
1. Re: JMS Transport
tom.elrod Nov 14, 2006 11:35 AM (in response to jgilbert)No plans for JMS transport within remoting.
-
2. Re: JMS Transport
jgilbert Nov 14, 2006 11:56 AM (in response to jgilbert)Do you think this is something reasonable that I should take a stab at or is there a better approach?
-
3. Re: JMS Transport
tom.elrod Nov 14, 2006 12:12 PM (in response to jgilbert)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.
-
4. Re: JMS Transport
jgilbert Nov 14, 2006 12:18 PM (in response to jgilbert)Makes sense.
I am just trying to reproduce the kind of capability with jbossws that i could do with the axis jms transport. -
5. Re: JMS Transport
tom.elrod Nov 14, 2006 12:47 PM (in response to jgilbert)Don't know the axis jms transport that well. What is the advantage of using that over http?
-
6. Re: JMS Transport
jgilbert Nov 14, 2006 6:30 PM (in response to 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 -
7. Re: JMS Transport
tom.elrod Nov 14, 2006 7:44 PM (in response to jgilbert)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.