RE: JMS Transport in Axis2
Hi Asankha, Going back to my original question, In this latest release will you have functionality to specify Reply-To property on client side? Thanks and Regards, Shital Joshi From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 11:21 PM To: Joshi, Shital; axis-user@ws.apache.org Subject: Re: JMS Transport in Axis2 Hi Shital Do you mean that next release of Axis2 say (Axis2_1_5) will not have code base for JMS Transport Yes.. and we'll have include ws-commons library to support JMS Transport? This will be done for you, most probably automatically with the Axis2 release.. but the specifics are yet to be sorted out.. one could argue not to ship the JMS and other transports by default with the Axis2 builds considering the size of the artifacts.. but it would be made very simple for users who want to use these transports, to make use of them. With the new structure, all transport code for Axis2 now comes from ws-commons, so its almost hidden from end users. I was thinking of extending org.apache.axis2.transport.jms.JMSSender and see if I can implement request-response operation. Do you think I should wait till next week and use your nightly builds? Yes,.. as a user you should not be worried about this level of the framework code. But you are more than welcome to join the dev lists and contribute to help make things better. asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
Re: JMS Transport in Axis2
Hi Shital Going back to my original question, In this latest release will you have functionality to specify Reply-To property on client side? Yes, a message context property JMS_REPLY_TO could set the reply destination, over which a client would wait for the response. I will inform the user list as soon as the new transport is officially checked in, so that everyone could test scenarios and give feedback, and we will address any issues if there are, promptly asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
JMS Transport in Axis2
Hi, I am attempting to use the JMS transport in Axis2. We are using Tibco queues. I was able to do one way operation (http://www.w3.org/TR/wsdl#_one-way) over JMS. When I tried to do request-response operation, I get client already exists JMS Exception. SEVERE: Failed to create a connection. The JMSException message is as follows: clientId already exists [ERROR] Error preparing to send message to destination javax.jms.InvalidClientIDException: clientId already exists How does the org.apache.axis2.transport.jms.JMSSender work? Can I specify different queue in JMSSender configuration? I tried this but it didn't work: transportSender name=jms class=org.apache.axis2.transport.jms.JMSSender parameter name=default parameter name=java.naming.factory.initialcom.gs.ContextFactory/parameter parameter name=transport.jms.ConnectionFactoryJNDINameQueueFactory/parameter /parameter /transportSender How can I pass reply-to parameter from client side? Thanks and Regards, Shital Joshi Goldman, Sachs Co. Prime Brokerage Technology 917-343-5780 [EMAIL PROTECTED]
Re: JMS Transport in Axis2
Hi Joshi I am attempting to use the JMS transport in Axis2. We are using* Tibco* queues. I was able to do one way operation (_http://www.w3.org/TR/wsdl#_one-way_) over JMS. When I tried to do request-response operation, I get client already exists JMS Exception. SEVERE: Failed to create a connection. The JMSException message is as follows: clientId already exists [ERROR] Error preparing to send message to destination *javax.jms.InvalidClientIDException: clientId already exists* How does the* org.apache.axis2.transport.jms.JMSSender* work? Can I specify different queue in JMSSender configuration? I tried this but it didn't work: transportSender name=jms class=org.apache.axis2.transport.jms.JMSSender parameter name=default parameter name=java.naming.factory.initialcom.gs.ContextFactory/parameter parameter name=transport.jms.ConnectionFactoryJNDINameQueueFactory/parameter /parameter /transportSender We are currently improving the JMS transport to be much more powerful and flexible, including proper support for durable subscriptions, and the good news is that its almost ready.. Would you be interested to work with us to help ensure that your use case is properly handled, as well as to give us feedback that will help us make it better? The discussions have been happening around the Apache Synapse mailing list [1] for now, and you are welcome to join asankha [1] http://markmail.org/message/6ewkmrdzszi2yijy -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
RE: JMS Transport in Axis2
Hello Asankha, I would be happy to work with your team. Do you have a date in mind for the release which has better JMS Transport? Thanks and Regards, Shital Joshi From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 1:08 PM To: axis-user@ws.apache.org Cc: Joshi, Shital Subject: Re: JMS Transport in Axis2 Hi Joshi I am attempting to use the JMS transport in Axis2. We are using Tibco queues. I was able to do one way operation (http://www.w3.org/TR/wsdl#_one-way http://www.w3.org/TR/wsdl#_one-way ) over JMS. When I tried to do request-response operation, I get client already exists JMS Exception. SEVERE: Failed to create a connection. The JMSException message is as follows: clientId already exists [ERROR] Error preparing to send message to destination javax.jms.InvalidClientIDException: clientId already exists How does the org.apache.axis2.transport.jms.JMSSender work? Can I specify different queue in JMSSender configuration? I tried this but it didn't work: transportSender name=jms class=org.apache.axis2.transport.jms.JMSSender parameter name=default parameter name=java.naming.factory.initialcom.gs.ContextFactory/parameter parameter name=transport.jms.ConnectionFactoryJNDINameQueueFactory/parameter /parameter /transportSender We are currently improving the JMS transport to be much more powerful and flexible, including proper support for durable subscriptions, and the good news is that its almost ready.. Would you be interested to work with us to help ensure that your use case is properly handled, as well as to give us feedback that will help us make it better? The discussions have been happening around the Apache Synapse mailing list [1] for now, and you are welcome to join asankha [1] http://markmail.org/message/6ewkmrdzszi2yijy -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
Re: JMS Transport in Axis2
Hi Shital I would be happy to work with your team. Do you have a date in mind for the release which has better JMS Transport? We are almost code complete.. but would need improved documentation and samples etc to supplement the new features. I would expect the code to be checked into svn by next week, and available with nightly builds. I do not know of any of the developers having access to a Tibco environment, and thus it would be great to get initial feedback from you. By the way, FYI the old transport code used by Axis2 (which was a fork from the code used by Apache Synapse sometime back) is now deprecated and removed from SVN, and the development of the common transports (such as JMS, Mail, etc ) takes place on WS-Commons sub-project.. asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
RE: JMS Transport in Axis2
Hello Asankha, Do you mean that next release of Axis2 say (Axis2_1_5) will not have code base for JMS Transport and we'll have include ws-commons library to support JMS Transport? I was thinking of extending org.apache.axis2.transport.jms.JMSSender and see if I can implement request-response operation. Do you think I should wait till next week and use your nightly builds? Thanks for your prompt response. Regards, Shital Joshi From: Asankha C. Perera [mailto:[EMAIL PROTECTED] Sent: Friday, November 14, 2008 2:13 PM To: axis-user@ws.apache.org Subject: Re: JMS Transport in Axis2 Hi Shital I would be happy to work with your team. Do you have a date in mind for the release which has better JMS Transport? We are almost code complete.. but would need improved documentation and samples etc to supplement the new features. I would expect the code to be checked into svn by next week, and available with nightly builds. I do not know of any of the developers having access to a Tibco environment, and thus it would be great to get initial feedback from you. By the way, FYI the old transport code used by Axis2 (which was a fork from the code used by Apache Synapse sometime back) is now deprecated and removed from SVN, and the development of the common transports (such as JMS, Mail, etc ) takes place on WS-Commons sub-project.. asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
Re: JMS Transport in Axis2
Hi Shital Do you mean that next release of Axis2 say (Axis2_1_5) will not have code base for JMS Transport Yes.. and we'll have include ws-commons library to support JMS Transport? This will be done for you, most probably automatically with the Axis2 release.. but the specifics are yet to be sorted out.. one could argue not to ship the JMS and other transports by default with the Axis2 builds considering the size of the artifacts.. but it would be made very simple for users who want to use these transports, to make use of them. With the new structure, all transport code for Axis2 now comes from ws-commons, so its almost hidden from end users. I was thinking of extending *org.apache.axis2.transport.jms.JMSSender* and see if I can implement request-response operation. Do you think I should wait till next week and use your nightly builds? Yes,.. as a user you should not be worried about this level of the framework code. But you are more than welcome to join the dev lists and contribute to help make things better. asankha -- Asankha C. Perera http://adroitlogic.org http://esbmagic.blogspot.com
