Re: WS Addressing :: http requests response (ReplyTo) on JMS protocol

2006-10-12 Thread Ali Sadik Kumlali
Hi Vaibhav,

By assuming following;
- You generate the service from WSDL
- Your client uses the generated stub
- Since your MEP is in-out, generated stub should return a value. But by using 
fireAndForget() you say "I don't mind the result over the same 
channel(connection)".

Then, as Brian suggested, you should follow the jms-transport document[1]. So;

At client side you should;
- enable WS-Addressing in axis2.xml

- set ReplyTo field to jms URI. For example:

   String jmsEndpointURL = "jms:/"

 + "QUEUE_JNDI_NAME" // destination

 + "?"

 + "transport.jms.ConnectionFactoryJNDIName="

 + "QUEUE_CONNECTION_FACTORY_JNDI_NAME"

 + 
"&java.naming.factory.initial=com.sonicsw.jndi.mfcontext.MFContextFactory" // 
vendor specific factory

 + "&java.naming.provider.url=tcp://localhost:2506" // vendor 
specific provider URL

 + "&java.naming.security.principal=Administrator"

 + "&java.naming.security.credentials=Administrator";

At service side, you should;
- enable WS-Addressing in axis2.xml

- use HTTP transport receiver and JMS transport sender in axis2.xml (This is 
already done for you:)
- add jms related definitions of your service to services.xml. For example:
  

   ...
  
 jms
  
  QUEUE_CONNECTION_FACTORY_JNDI_NAME
  QUEUE_JNDI_NAME

  

I didn't try in-out MEP with JMS and not sure whether JMS URI in ReplyTo is 
handled properly. Just give it a try, and please let us know the result :)

Regards,

Ali Sadik Kumlali

[1] 
http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1/jms-transport.html


- Original Message 
From: Vaibhav Pandey <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org
Sent: Wednesday, October 11, 2006 5:06:45 PM
Subject: RE: WS Addressing :: http requests response (ReplyTo) on JMS protocol

Hi,
-yaa m using axis2.1.1 (nightly built)
-MEP is INOUT with method call as fireandforget()
-i want my nonblockingclient to send the request to a simple WS whose
response should be forwarded to a different JMS WS hosted on a different
application server


CLIENT Request> WS 1(simple WS) ---Response on a queue after
lookup---> WS 2(JMS WS listening on this queue)


Regards,
Vaibhav


-Original Message-----
From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 11, 2006 6:19 PM
To: axis-user@ws.apache.org
Subject: Re: WS Addressing :: http requests response (ReplyTo) on JMS
protocol


Hi Vaibhav,

- Do you use Axis2? If so, please add [Axis2] to the mail subject for easier
follow up. Following questions assume you are using Axis2.
- What kind of MEP do you use? If I understand correctly, you use in-out
MEP.
- Do you expect nonBlockingDualClient to listents to the response over a MDB
instead of creating a listener by itself?

Regards,

Ali Sadik Kumlali

----- Original Message 
From: Vaibhav Pandey <[EMAIL PROTECTED]>
To: Axis-User 
Sent: Wednesday, October 11, 2006 8:31:10 AM
Subject: WS Addressing :: http requests response (ReplyTo) on JMS protocol

Hi All,
I am working on a scenario were my nonBlockingDualClient sends a http
request to a WS and the response should go to a JMS listener listening on a
different port. in short i want the response to go via JMS into the
queue on which my listener is listening so that i can do some processing on
it as and when it arrives at MDB's OnMessage().

I have already implemented an HTTP to HTTP scenario and m in need of some
guidance in this HTTP-JMS scenario on the configurations required in my
client to forward the request on JMS.

Any help is highly appreciated !!


Regards,
Vaibhav



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]









-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: WS Addressing :: http requests response (ReplyTo) on JMS protocol

2006-10-11 Thread Vaibhav Pandey
Hi,
-yaa m using axis2.1.1 (nightly built)
-MEP is INOUT with method call as fireandforget()
-i want my nonblockingclient to send the request to a simple WS whose
response should be forwarded to a different JMS WS hosted on a different
application server


CLIENT Request> WS 1(simple WS) ---Response on a queue after
lookup---> WS 2(JMS WS listening on this queue)


Regards,
Vaibhav


-Original Message-
From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 11, 2006 6:19 PM
To: axis-user@ws.apache.org
Subject: Re: WS Addressing :: http requests response (ReplyTo) on JMS
protocol


Hi Vaibhav,

- Do you use Axis2? If so, please add [Axis2] to the mail subject for easier
follow up. Following questions assume you are using Axis2.
- What kind of MEP do you use? If I understand correctly, you use in-out
MEP.
- Do you expect nonBlockingDualClient to listents to the response over a MDB
instead of creating a listener by itself?

Regards,

Ali Sadik Kumlali

- Original Message 
From: Vaibhav Pandey <[EMAIL PROTECTED]>
To: Axis-User 
Sent: Wednesday, October 11, 2006 8:31:10 AM
Subject: WS Addressing :: http requests response (ReplyTo) on JMS protocol

Hi All,
I am working on a scenario were my nonBlockingDualClient sends a http
request to a WS and the response should go to a JMS listener listening on a
different port. in short i want the response to go via JMS into the
queue on which my listener is listening so that i can do some processing on
it as and when it arrives at MDB's OnMessage().

I have already implemented an HTTP to HTTP scenario and m in need of some
guidance in this HTTP-JMS scenario on the configurations required in my
client to forward the request on JMS.

Any help is highly appreciated !!


Regards,
Vaibhav



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: WS Addressing :: http requests response (ReplyTo) on JMS protocol

2006-10-11 Thread Brian De Pradine

Hello Vaibhav,

I don't think that there is any documentation
covering this scenario at the moment, but feel free to contribute some
when you finally get it working :-)

I would expect the scenario to work,
using axis2 1.1, even though I am not sure how you would go about setting
up the JMS resources that you would need. (however, I believe that you
will find some information on that here [1].)

As far as addressing is concerned, you
should set up your client exactly as you did for your HTTP - HTTP scenario,
except this time the address of your ReplyTo EPR should be a URI of the
form "jms:".

[1] http://svn.apache.org/repos/asf/webservices/axis2/branches/java/1_1/xdocs/1_1/jms-transport.html

Cheers

Brian DePradine
Web Services Development
IBM Hursley
External  +44 (0) 1962 816319         Internal
246319

If you can't find the time to do it right the first time, where will you
find the time to do it again?


"Vaibhav Pandey" <[EMAIL PROTECTED]>
wrote on 11/10/2006 06:31:10:

> Hi All,
> I am working on a scenario were my nonBlockingDualClient sends a http
> request to a WS and the response should go to a JMS listener listening
on a
> different port. in short i want the response to go via JMS into
the
> queue on which my listener is listening so that i can do some processing
on
> it as and when it arrives at MDB's OnMessage().
> 
> I have already implemented an HTTP to HTTP scenario and m in need
of some
> guidance in this HTTP-JMS scenario on the configurations required
in my
> client to forward the request on JMS.
> 
> Any help is highly appreciated !!
> 
> 
> Regards,
> Vaibhav
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


Re: WS Addressing :: http requests response (ReplyTo) on JMS protocol

2006-10-11 Thread Ali Sadik Kumlali
Hi Vaibhav,

- Do you use Axis2? If so, please add [Axis2] to the mail subject for easier 
follow up. Following questions assume you are using Axis2.
- What kind of MEP do you use? If I understand correctly, you use in-out MEP.
- Do you expect nonBlockingDualClient to listents to the response over a MDB 
instead of creating a listener by itself?

Regards,

Ali Sadik Kumlali

- Original Message 
From: Vaibhav Pandey <[EMAIL PROTECTED]>
To: Axis-User 
Sent: Wednesday, October 11, 2006 8:31:10 AM
Subject: WS Addressing :: http requests response (ReplyTo) on JMS protocol 

Hi All,
I am working on a scenario were my nonBlockingDualClient sends a http
request to a WS and the response should go to a JMS listener listening on a
different port. in short i want the response to go via JMS into the
queue on which my listener is listening so that i can do some processing on
it as and when it arrives at MDB's OnMessage().

I have already implemented an HTTP to HTTP scenario and m in need of some
guidance in this HTTP-JMS scenario on the configurations required in my
client to forward the request on JMS.

Any help is highly appreciated !!


Regards,
Vaibhav



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



WS Addressing :: http requests response (ReplyTo) on JMS protocol

2006-10-10 Thread Vaibhav Pandey
Hi All,
I am working on a scenario were my nonBlockingDualClient sends a http
request to a WS and the response should go to a JMS listener listening on a
different port. in short i want the response to go via JMS into the
queue on which my listener is listening so that i can do some processing on
it as and when it arrives at MDB's OnMessage().

I have already implemented an HTTP to HTTP scenario and m in need of some
guidance in this HTTP-JMS scenario on the configurations required in my
client to forward the request on JMS.

Any help is highly appreciated !!


Regards,
Vaibhav



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]