Hi David, Kindly hav a look at the SOAP req/res that i captured:-
My flow is WSAD client--> JBoss WS1 --> RAD WS2 1) SOAP Request from WSAD client to JBoss service:- POST /axis2/services/WSAddressing HTTP/1.1 SOAPAction: "urn:echo" User-Agent: Axis2 Host: 127.0.0.1:8089 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 290 <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><w sa:To>http://127.0.0.1:8089/axis2/services/WSAddressing</wsa:To><wsa:ReplyTo ><wsa:Address>http://127.0.0.1:7390/WSDLStyleTrial/services/WSDLRpcTesting</ wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:C41E22A1B9F671E78211648895 068281</wsa:MessageID><wsa:Action>urn:echo</wsa:Action></soapenv:Header><soa penv:Body><example1:echo xmlns:example1="http://example1.userguide/xsd";><example1:Text>Axis2 Echo String </example1:Text></example1:echo></soapenv:Body></soapenv:Envelope> 0 2) SOAP Response from JBoss service to RAD service:- POST /WSDLStyleTrial/services/WSDLRpcTesting HTTP/1.1 User-Agent: Axis/2.0 SOAPAction: urn:echo Host: localhost:9080 Transfer-Encoding: chunked Content-Type: text/xml; charset=UTF-8 <?xml version="1.0" encoding="http://schemas.xmlsoap.org/soap/envelope/";?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsa="http://www.w3.org/2005/08/addressing";> <soapenv:Header> <wsa:To>http://127.0.0.1:7390/WSDLStyleTrial/services/WSDLRpcTesting</wsa:To > <wsa:ReplyTo> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address> </wsa:ReplyTo> <wsa:From> <wsa:Address>http://127.0.0.1:8089/axis2/services/WSAddressing</wsa:Address> </wsa:From> <wsa:FaultTo> <wsa:Address>http://127.0.0.1:8089/axis2/services/WSAddressing</wsa:Address> </wsa:FaultTo> <wsa:MessageID>urn:uuid:83DE8306AF7616260911648895071715</wsa:MessageID> <wsa:Action>urn:echo</wsa:Action> <wsa:RelatesTo wsa:RelationshipType="wsa:Reply">urn:uuid:C41E22A1B9F671E78211648895068281</ wsa:RelatesTo> </soapenv:Header> <soapenv:Body> <ns:echoResponse xmlns:ns="http://example1.userguide/xsd";> <return>vaibhav</return> </ns:echoResponse> </soapenv:Body> </soapenv:Envelope> 3) Fault from RAD service:- HTTP/1.1 500 Internal Server Error Content-Type: text/xml; charset=utf-8 Content-Language: en-US Content-Length: 3118 Date: Thu, 30 Nov 2006 12:25:07 GMT <soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header/> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Client</faultcode> <faultstring><![CDATA[WSWS3277E: Error: Could not resolve to an operation. The message contains an element named ""{http://example1.userguide/xsd}echoResponse"";, but this does not match any operation of the target port. Debug: name: services/WSDLRpcTesting implClass: class wsdlSample.WSDLRpcTesting implClassLoader: [EMAIL PROTECTED] Local ClassPath: D:\D-Backup\RAD_WS_workspace\WSDL_Style_Checking-RPC-DOCetc_workspace\WSDLSt yleTrial\WebContent\WEB-INF\classes;D:\D-Backup\RAD_WS_workspace\WSDL_Style_ Checking-RPC-DOCetc_workspace\WSDLStyleTrial\WebContent\WEB-INF\lib\axis.jar ;D:\D-Backup\RAD_WS_workspace\WSDL_Style_Checking-RPC-DOCetc_workspace\WSDLS tyleTrial\WebContent\WEB-INF\lib\commons-discovery.jar;D:\D-Backup\RAD_WS_wo rkspace\WSDL_Style_Checking-RPC-DOCetc_workspace\WSDLStyleTrial\WebContent\W EB-INF\lib\commons-logging.jar;D:\D-Backup\RAD_WS_workspace\WSDL_Style_Check ing-RPC-DOCetc_workspace\WSDLStyleTrial\WebContent\WEB-INF\lib\jaxrpc.jar;D: \D-Backup\RAD_WS_workspace\WSDL_Style_Checking-RPC-DOCetc_workspace\WSDLStyl eTrial\WebContent\WEB-INF\lib\log4j-1.2.4.jar;D:\D-Backup\RAD_WS_workspace\W SDL_Style_Checking-RPC-DOCetc_workspace\WSDLStyleTrial\WebContent\WEB-INF\li b\saaj.jar;D:\D-Backup\RAD_WS_workspace\WSDL_Style_Checking-RPC-DOCetc_works pace\WSDLStyleTrial\WebContent\WEB-INF\lib\wsdl4j.jar;D:\D-Backup\RAD_WS_wor kspace\WSDL_Style_Checking-RPC-DOCetc_workspace\WSDLStyleTrial\WebContent; Delegation Mode: PARENT_FIRST defaultNS: null endpointURL: null OperationDesc[0]: name: getMessage returnQName: getMessageReturn returnType: {http://www.w3.org/2001/XMLSchema}string returnClass: class java.lang.String elementQName:{http://wsdlSample}getMessage soapAction: style: wrapped use: literal numInParams: 1 properties: KEY(inputMessageQName) VALUE({http://wsdlSample}getMessageRequest) KEY(outputMessageQName) VALUE({http://wsdlSample}getMessageResponse) KEY(inputName) VALUE(getMessageRequest) KEY(outputName) VALUE(getMessageResponse) KEY(portTypeQName) VALUE({http://wsdlSample}WSDLRpcTesting) KEY(targetNamespace) VALUE(http://wsdlSample) KEY(buildNum) VALUE(o0444.10) method:public java.lang.String wsdlSample.WSDLRpcTesting.getMessage(java.lang.String) ParameterDesc[0]: identity: [EMAIL PROTECTED] name: name mode: IN isReturn: false typeQName: {http://www.w3.org/2001/XMLSchema}string javaType: class java.lang.String javaSigType:class java.lang.String inHeader: false outHeader: false minOccursIs0:false maxOccursIs1:true properties: ]]></faultstring> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> Regards, Vaibhav -----Original Message----- From: David Illsley [mailto:[EMAIL PROTECTED] Sent: Thursday, November 30, 2006 2:22 PM To: [email protected] Subject: Re: WS-Addressing setReplyto method name namespace Hi, I'm not an expert on RAD6 by any stretch of the imagination but I don't think it supports operation identification based on the wsa:Action field. If that's the case then you'll need to make the response message body from JBoss look like the request message that RAD6 is expecting. David On 30/11/06, Vaibhav Pandey <[EMAIL PROTECTED]> wrote: > Hi Michele, > The process cycle is that: my client sends a message to a service hosted on > JBoss with all WS addressing properties like replyTo, faultTo, from, to etc. > already mentioned in the request header. Now, the request header in this > case has a replyTo set to the address of the service installed on > RAD6(service up and running). Now when i start the process then the message > as specified goes to the JBoss service and then based on the replyTo address > hits the RAD6 server. After this i get a SOAP fault from RAD6 (also shown on > the RAD6 console- so this means that my message had reached the destination > but then its throwing the SOAP fault that it cannot map the operation name > to any operation name in the service). This is absolutely fine as the RAD > servie excepts a string type param and the response from JBoss also contains > a string param but there is no method name of the destination rad service in > this reponse (as a SOAP response does not contain a method name) so its > unable to map to the response from Jboss to rad. > > My basic aim is that i want to simulate a scenario wherein i pass a string > (or any data) from a clent to a service (using WS addessing) and then that > service after manipulating that data sends it to another sevice hosted > somewhere else. Is the way i m implementing it correct or is there any other > way ? Also what i feel is that if i want to add the method name in the > response of Jboss service then may be will have to use SAAJ api's but think > thats not a correct way of doing !! > > My client uses axis 2 Api's. > > Kindly guide......... > > > Regards, > Vaibhav > > > > > -----Original Message----- > From: Michele Mazzucco [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 29, 2006 9:49 PM > To: [email protected] > Subject: Re: WS-Addressing setReplyto method name namespace > > > Hi Vaibhav, > > Is the message sent by jboss to RAD6 a forward or a result message? > In the first case you must be sure the target service is available on > RAD6, in the latter one you have to fix the addressing information > contained into the SOAP header before the message hits the RAD6 host > (by default the replyTo fields is set to the client so if you send > the message somewhere else the receiver will fail). > > And what about the exception your service is throwing? Try to post it > and maybe we can help you. > > > Regards, > Michele > > > On 29 Nov 2006, at 13:54, Vaibhav Pandey wrote: > > > Hi, > > need help on an issue relating to WS Addressing: > > m working on the following configuration with WS addressing using > > axis2 :- > > > > axis2 + Jboss + IBM Rad6 > > > > m trying to generate a scenario wherein i send a SOAP request using > > axis2 to > > an axis2 WS deployed on JBOSS. Then the reply of this service > > should be > > forwarded to another WS hosted on RAD6. Everythng wrks perfectly > > fine except > > the fault that i get from RAD6 stating that it could not map the > > request to > > a particular operation > > > > axis2 client --SOAPReq (over HTTP)--> WS1 (axis2 WS on jboss) -- > > SOAPRes > > (over HTTP)--> WS2 (on IBM Rad6) > > > > The reason for this is that the SOAP response generated by my WS1 > > will have > > the namespace and method response of WS1 and no information > > pertaining to > > the WS2, but as the replyto header is set to the WS2 EPR, the > > request gets > > forwarded and then the WS2 generates a fault. > > > > I tried with all types of WS viz doc/literal, rpc/encoded, rpc/ > > literal etc > > but got the same fault !! > > > > > > > > Is there any way by which i can set these configurations(method > > name of WS2 > > and namespace through my client itself or any other way) ?? > > > > Kindly guide me as to what m i supposed to do ?? > > > > > > 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] > > -- David Illsley - IBM Web Services Development --------------------------------------------------------------------- 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]
