RE: Transport specification for web services
Hi Martin, Thanks for the response. I am aware that Axis2 supports multiple transport frameworks. My question is - can we deploy web services on the same Axis2 engine that communicate with client using different transport network. For example, say web service A communicates using default HTTP and web service B communicates using TCP and both these web services are deployed on the same server. Is this scenario possible ? I was thinking if it was possible to specify in the services.xml file for each web service but I couldn't locate any parameter that specifies that. Regards, -Lokesh From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2008 5:55 PM To: axis-user@ws.apache.org Subject: RE: Transport specification for web services AXIS supports a number of different transports If you want to implement AXIS via JMS take a look at IBM's JMS Tutorial http://www.ibm.com/developerworks/webservices/library/ws-jms/ Anyone ? Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: Transport specification for web services Date: Tue, 12 Aug 2008 16:43:28 -0700 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Hi, I need to specify transport specification for some web services. The default for the axis2 is HTTP and I want to keep it like that. But I do want some of my web services to connect to their client with TCP. Is it possible to specify transport mechanism different from other services on the same axis2 deployment. Thanks Regards, -Lokesh Get more from your digital life. Find out how. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008
Re: Transport specification for web services
Kumar, Lokesh wrote: Hi Martin, Thanks for the response. I am aware that Axis2 supports multiple transport frameworks. My question is – can we deploy web services on the same Axis2 engine that communicate with client using different transport network. For example, say web service A communicates using default HTTP and web service B communicates using TCP and both these web services are deployed on the same server. Is this scenario possible ? TCP and HTTP needs separate listeners. Now, if your server can handle both HTTP and TCP listeners simultaneously this could be done. But the usual norm is that, HTTP endpoint would be different form TCP endpoint. They should simply listen on different ports. Samisa... I was thinking if it was possible to specify in the services.xml file for each web service but I couldn’t locate any parameter that specifies that. Regards, -Lokesh *From:* Martin Gainty [mailto:[EMAIL PROTECTED] *Sent:* Tuesday, August 12, 2008 5:55 PM *To:* axis-user@ws.apache.org *Subject:* RE: Transport specification for web services AXIS supports a number of different transports If you want to implement AXIS via JMS take a look at IBM's JMS Tutorial http://www.ibm.com/developerworks/webservices/library/ws-jms/ Anyone ? Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: Transport specification for web services Date: Tue, 12 Aug 2008 16:43:28 -0700 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Hi, I need to specify transport specification for some web services. The default for the axis2 is HTTP and I want to keep it like that. But I do want some of my web services to connect to their client with TCP. Is it possible to specify transport mechanism different from other services on the same axis2 deployment. Thanks Regards, -Lokesh Get more from your digital life. Find out how. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008 -- Samisa Abeysinghe http://people.apache.org/~samisa/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Transport specification for web services
Hi, I need to specify transport specification for some web services. The default for the axis2 is HTTP and I want to keep it like that. But I do want some of my web services to connect to their client with TCP. Is it possible to specify transport mechanism different from other services on the same axis2 deployment. Thanks Regards, -Lokesh
RE: Transport specification for web services
AXIS supports a number of different transports If you want to implement AXIS via JMS take a look at IBM's JMS Tutorial http://www.ibm.com/developerworks/webservices/library/ws-jms/ Anyone ? Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: Transport specification for web services Date: Tue, 12 Aug 2008 16:43:28 -0700 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Hi, I need to specify transport specification for some web services. The default for the axis2 is HTTP and I want to keep it like that. But I do want some of my web services to connect to their client with TCP. Is it possible to specify transport mechanism different from other services on the same axis2 deployment. Thanks Regards, -Lokesh _ Get more from your digital life. Find out how. http://www.windowslive.com/default.html?ocid=TXT_TAGLM_WL_Home2_082008
