• Post Reply Bookmark Topic Watch Topic
  • New Topic

solicit response error using RAD  RSS feed

 
Ayub ali khan
Ranch Hand
Posts: 395
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I am trying to generate jax-rpc client from an existing wsdl file using RAD 7.5 on portal 6.1 server. I get the below error during this process:

IWAB0639E Error in generating Java files and deployment descriptors from WSDL file
GetEmployeeDetails is a solicit-response style operation and is unsupported.

Below is the wsdl port type definition:



if I change it the below the client generation completes without issues. Could any one suggest whether its fine to change in this way if not how to generate the client using the original wsdl definition on RAD.



Thank you

--Ayub

 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ayub ali khan wrote:Could any one suggest whether its fine to change in this way if not how to generate the client using the original wsdl definition on RAD.


Well, it depends. The modified version describes an In-Out (Request-Response) message exchange where the consumer contacts the provider and the provider responds. The original version describes an Out-In (Solicit-Response) message exchange where the provider contacts the consumer and the consumer responds.

So if you intended a request-response message exchange then you are fine with the modified version. If you are looking for a solicit-response message exchange then JAX-RPC is the wrong API because it only supports request-response and one-way; JAX-RPC does not support the solicit-response or notification message exchange patterns. The work around is to make the "consumer" another web service and have the "provider" access that web service as a client.

Message Exchange Patterns as describable by WSDL 1.1 (but not necessarily supported by JAX-RPC):

In-Out (Request-Response)
<operation name="...">
<input message="..." />
<output message="..." />
</operation>


In-Only (One-Way)
<operation name="...">
<input message="..." />
</operation>


Out-In (Solicit-Response)
<operation name="...">
<output message="..." />
<input message="..." />
</operation>


Out-Only (Notification)
<operation name="...">
<output message="..." />
</operation>
 
Ayub ali khan
Ranch Hand
Posts: 395
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Peer!!! I understand your point
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!