I pretty sure of the answer, but I just want to make sure. Can you call jax-rpc and jaxm implemented web services from non-java clients?
Thanks.
-
JWSDP and Non-Java Clients (3 messages)
- Posted by: Sean Cohan
- Posted on: March 25 2004 12:02 EST
Threaded Messages (3)
- JWSDP and Non-Java Clients by dj ebola on March 25 2004 12:31 EST
- RE: JWSDP and Non-Java Clients by Sean Cohan on March 25 2004 12:48 EST
- JWSDP and Non-Java Clients by Sean Cohan on April 02 2004 10:42 EST
-
JWSDP and Non-Java Clients[ Go to top ]
- Posted by: dj ebola
- Posted on: March 25 2004 12:31 EST
- in response to Sean Cohan
Yes, not a problem.
Easy to test with a .NET client, just generate the client and point to the location of the wdsl-document for your web service. -
RE: JWSDP and Non-Java Clients[ Go to top ]
- Posted by: Sean Cohan
- Posted on: March 25 2004 12:48 EST
- in response to Sean Cohan
Thought so. Thanks for confirming. -
JWSDP and Non-Java Clients[ Go to top ]
- Posted by: Sean Cohan
- Posted on: April 02 2004 10:42 EST
- in response to Sean Cohan
A follow up: In the book "Developing Java Web Services", Wiley Publishing, a diagram (pg 455) shows that jax-rpc request/response communication travels from jax-rpc runtime to jax-rpc runtime where the client is in a J2SE environment. This leads me to believe that your client must be java based. Am I missing something here? Can you call the jax-rpc from a non-java client?
Also in the same book, another diagram (pg 405) depicts jaxm request/response communication between and a non java soap client and jaxm provider. For sync/asynchronous, communication is between jaxm provider and jaxm provider. Does this mean, with jaxm, I can have non java clients for synchrounous comm, but for asynchronous comm I have to have java clients?
Thanks.