Hi Freeman,

>>Are you sure for sendValidateLocationOutput message
>><wsdl:part name="HeaderRS" element="gr:HeaderRQ"/>
>>Is it correct?

>>Isn't it should be 
>><wsdl:part name="HeaderRS" element="gr:HeaderRS"/>

>>As you have different schema for RQ and RS.

Yes, i was testing if for some reason the HeaderRS type was wrong but
HeaderRS and HeaderRQ types are amlost the same...



>>Also, as you have a complex wsdl, the better way for development IMHO is
you use standalone cxf >>client/server firstly to do the test, once you make
the communication successfully between cxf client >>and server then you can
deploy it in to smx container with servicemix-cxf-bc/se. That's easy for you
>>to locate problem and debug.

Ok i will try it then...

Thanks for the help!

Santiago.



Freeman Fang wrote:
> 
> Hi,
> 
> There should be something wrong from your wsdl.
> I found somthing migth be wrong.
> 
> Look at
>       <wsdl:message name="sendValidateLocationInput">
>               <wsdl:part name="HeaderRQ" element="gr:HeaderRQ"/>
>               <wsdl:part name="ValidateLocationRQ"
> element="gr:ValidateLocationRQ"/>
>       </wsdl:message>
>       <wsdl:message name="sendValidateLocationOutput">
>               <wsdl:part name="HeaderRS" element="gr:HeaderRQ"/>
>               <wsdl:part name="ValidateLocationRS"
> element="gr:ValidateLocationRS"/>
>       </wsdl:message>
> 
> Are you sure for sendValidateLocationOutput message
> <wsdl:part name="HeaderRS" element="gr:HeaderRQ"/>
> Is it correct?
> 
> Isn't it should be 
> <wsdl:part name="HeaderRS" element="gr:HeaderRS"/>
> 
> As you have different schema for RQ and RS.
> 
> Also, as you have a complex wsdl, the better way for development IMHO is
> you use standalone cxf client/server firstly to do the test, once you make
> the communication successfully between cxf client and server then you can
> deploy it in to smx container with servicemix-cxf-bc/se. That's easy for
> you to locate problem and debug.
> 
> 
> Freeman
> 
> smontico wrote:
>> 
>> Hi Freeman,
>> 
>> This is the information registered in the log file:
>> 
>> 13:23:41,431 | INFO  | 22792...@qtp4-0  | LoggingInInterceptor            
>> | .cxf.phase.PhaseInterceptorChain  226 | Inbound Message
>> ----------------------------
>> Encoding: UTF-8
>> Headers: {content-type=[text/xml;charset="utf-8"],
>> connection=[keep-alive], Host=[localhost:8193], Content-Length=[756],
>> User-Agent=[JAX-WS RI 2.1.6], Accept=[text/xml, multipart/related,
>> text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2], Soapaction=[""]}
>> Messages: 
>> Message:
>> 
>> Payload: <?xml version="1.0" ?><S:Envelope
>> xmlns:S="http://schemas.xmlsoap.org/soap/envelope/";><S:Body><HeaderRQ
>> xmlns="http://com/crs/sag/service";><Session
>> id="Id-239299043"><SourceIp>SourceIp1327922147</SourceIp><SessionStart>2010-03-11T13:20:24.616-02:00</SessionStart><SessionExpire>2010-03-11T13:20:24.617-02:00</SessionExpire></Session><Requester
>> id="Id-1514014488"><Organization>Organization369441417</Organization><Application>Application-285441110</Application><UserProfile><Role>Role1946970857</Role><User>User-1935780875</User></UserProfile><ChannelType>ChannelType1649789260</ChannelType></Requester><Request
>> TimeStamp="2010-03-11T13:20:24.619-02:00"
>> Id="Id-770032095"><Structure>Structure199201325</Structure></Request></HeaderRQ></S:Body></S:Envelope>
>> 
>> 
>> 
>> 13:23:41,474 | INFO  | 22792...@qtp4-0  | LoggingOutInterceptor           
>> | apache.cxf.io.CachedOutputStream  164 | Outbound Message
>> ---------------------------
>> Encoding: UTF-8
>> Headers: {}
>> Messages: 
>> Payload: <soap:Envelope
>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><HeaderRQ
>> xmlns="http://com/crs/sag/service";><Session
>> id="Id-1747858385"><SourceIp>SourceIp-1121417186</SourceIp><SessionStart>2010-03-09T15:56:33.092-02:00</SessionStart><SessionExpire>2010-03-09T15:56:33.093-02:00</SessionExpire></Session><Requester
>> id="Id2092953575"><Organization>Organization369786598</Organization><Application>Application-1162026762</Application><UserProfile><Role>Role-936522854</Role><User>User-1586469395</User></UserProfile><ChannelType>ChannelType1424850953</ChannelType></Requester><Request
>> Id="Id-1167113949"
>> TimeStamp="2010-03-09T15:56:33.095-02:00"><Structure>Structure1120485559</Structure></Request></HeaderRQ><ValidateLocationRS
>> xmlns="http://com/crs/sag/service"; /></soap:Body></soap:Envelope>
>> 
>> 
>> It's seems that only the first body part (input and output) is included
>> in the payload but i dont know why...
>> I use the wsdl eclipse plugin to validate the wsdl file and it seems to
>> be correct.
>> Even if the wsdl is valid can be a problem in how i create the wsdl or
>> maybe something else?
>> 
>> I'm kind of lost...
>> 
>> Thanks again, Santiago.
>> 
>> 
>> Freeman Fang wrote:
>>> 
>>> Hi Santiago,
>>> 
>>> Your SA contain cxf bc endpoint and cxf se endpoint, right?
>>> If so, you can add something like
>>> <cxfbc:inInterceptors>
>>>            <bean  
>>> class="org.apache.cxf.interceptor.LoggingInInterceptor"/>
>>>          </cxfbc:inInterceptors>
>>>          <cxfbc:outInterceptors>
>>>            <bean  
>>> class="org.apache.cxf.interceptor.LoggingOutInterceptor"/>
>>>          </cxfbc:outInterceptors>
>>>          <cxfbc:inFaultInterceptors>
>>>            <bean  
>>> class="org.apache.cxf.interceptor.LoggingInInterceptor"/>
>>>          </cxfbc:inFaultInterceptors>
>>>          <cxfbc:outFaultInterceptors>
>>>            <bean  
>>> class="org.apache.cxf.interceptor.LoggingOutInterceptor"/>
>>>          </cxfbc:outFaultInterceptors>
>>> to your cxfbc:consumer endpoint configuration.
>>> 
>>> Freeman
>>> 
>>> On 2010-3-11, at 下午8:13, smontico wrote:
>>> 
>>>>
>>>> Hi Freeman, thanks again for answering my questions :)
>>>>
>>>> I'm new with servicemix could you tell me how to do what you are  
>>>> telling me,
>>>> please?
>>>>
>>>> Thanks, Santiago.
>>>>
>>>>
>>>> Freeman Fang wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Could you add LoggingOutInterceptor  and LoggingOutInterceptor for
>>>>> your cxf bc consumer to get the soap payload between your standalone
>>>>> client and http listener?
>>>>> You can see if the soap out message is correct to your client.
>>>>>
>>>>> Freeman
>>>>> On 2010-3-11, at 上午12:52, smontico wrote:
>>>>>
>>>>>>
>>>>>> I have cheked in the servicemix.log file and the out message of the
>>>>>> webservice operation is not null...
>>>>>>
>>>>>> Any Help ?
>>>>>>
>>>>>> Thanks, Santiago.
>>>>>>
>>>>>>
>>>>>> smontico wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I have deployed a cxf sa into servicemix 4, the webservice
>>>>>>> operation has 4
>>>>>>> arguments, 2 for in parameters and 2 for out parameters.
>>>>>>> I dont know why, one of the 2 out parameters is not modified when i
>>>>>>> received the response from the webservice operation but it is
>>>>>>> modified in
>>>>>>> the server side, the other object is modified correclty.
>>>>>>>
>>>>>>> Could be something in my wsdl ?
>>>>>>>
>>>>>>> This is my wsdl:
>>>>>>>
>>>>>>>
>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>> <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>>>>>>> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>>>>>>> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
>>>>>>> xmlns:xs="http://www.w3.org/2001/XMLSchema";
>>>>>>> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
>>>>>>> xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
>>>>>>> xmlns:gr="http://com/crs/sag/service";
>>>>>>> xmlns:tns="http://com/crs/sag/service"; name="validateLocation"
>>>>>>> targetNamespace="http://com/crs/sag/service";>
>>>>>>>         <wsdl:types>
>>>>>>>                 <xs:schema targetNamespace="http://com/crs/sag/service";
>>>>>>> elementFormDefault="qualified">
>>>>>>>                         <xs:include 
>>>>>>> schemaLocation="ValidateLocationRQ.xsd"/>
>>>>>>>                         <xs:include 
>>>>>>> schemaLocation="ValidateLocationRS.xsd"/>
>>>>>>>                         <xs:include 
>>>>>>> schemaLocation="../Common_Usage/HeaderRQ.xsd"/>
>>>>>>>                         <xs:include 
>>>>>>> schemaLocation="../Common_Usage/HeaderRS.xsd"/>
>>>>>>>                 </xs:schema>
>>>>>>>         </wsdl:types>
>>>>>>>         <wsdl:message name="sendValidateLocationInput">
>>>>>>>                 <wsdl:part name="HeaderRQ" element="gr:HeaderRQ"/>
>>>>>>>                 <wsdl:part name="ValidateLocationRQ"
>>>>>>> element="gr:ValidateLocationRQ"/>
>>>>>>>         </wsdl:message>
>>>>>>>         <wsdl:message name="sendValidateLocationOutput">
>>>>>>>                 <wsdl:part name="HeaderRS" element="gr:HeaderRQ"/>
>>>>>>>                 <wsdl:part name="ValidateLocationRS"
>>>>>>> element="gr:ValidateLocationRS"/>
>>>>>>>         </wsdl:message>
>>>>>>>         <wsdl:portType name="GeographicReferenceType">
>>>>>>>                 <wsdl:operation name="ValidateLocation">
>>>>>>>                         <wsdl:input 
>>>>>>> message="gr:sendValidateLocationInput"/>
>>>>>>>                         <wsdl:output 
>>>>>>> message="gr:sendValidateLocationOutput"/>
>>>>>>>                 </wsdl:operation>
>>>>>>>         </wsdl:portType>
>>>>>>>         <wsdl:binding name="validateLocationSOAPBinding"
>>>>>>> type="tns:GeographicReferenceType">
>>>>>>>                 <soap:binding style="document"
>>>>>>> transport="http://schemas.xmlsoap.org/soap/http"/>
>>>>>>>                 <wsdl:operation name="ValidateLocation">
>>>>>>>                         <wsdl:input>
>>>>>>>                                 <soap:body use="literal" 
>>>>>>> parts="ValidateLocationRQ"/>
>>>>>>>                                 <soap:body use="literal" 
>>>>>>> parts="HeaderRQ"/>                             
>>>>>>>                         </wsdl:input>
>>>>>>>                         <wsdl:output>
>>>>>>>                                 <soap:body use="literal" 
>>>>>>> parts="ValidateLocationRS"/>
>>>>>>>                                 <soap:body use="literal" 
>>>>>>> parts="HeaderRQ"/>
>>>>>>>                         </wsdl:output>
>>>>>>>                 </wsdl:operation>
>>>>>>>         </wsdl:binding>
>>>>>>>         <wsdl:service name="ValidateLocationService">
>>>>>>>                 <wsdl:port name="ValidateLocation"
>>>>>>> binding="tns:validateLocationSOAPBinding">
>>>>>>>                         <soap:address
>>>>>>> location="http://localhost:8193/ValidateLocationService/"/>
>>>>>>>                 </wsdl:port>
>>>>>>>         </wsdl:service>
>>>>>>> </wsdl:definitions>
>>>>>>>
>>>>>>> This is the webservice operation:
>>>>>>>
>>>>>>> @WebService(name = "ValidateLocationService", targetNamespace =
>>>>>>> "http://com/crs/sag/service"; , endpointInterface =
>>>>>>> "com.crs.sag.service.GeographicReferenceType")
>>>>>>> public class GeographicReferenceTypeImpl implements
>>>>>>> GeographicReferenceType{
>>>>>>>
>>>>>>>         public void validateLocation(HeaderRQ headerRQ,
>>>>>>>                         ValidateLocationRQ validateLocationRQ, 
>>>>>>> Holder<HeaderRQ>  
>>>>>>> headerRS,
>>>>>>>                         Holder<ValidateLocationRS> validateLocationRS) {
>>>>>>>
>>>>>>>
>>>>>>> In the server i set an instance of HeaderRQ into headerRS.value but
>>>>>>> when i
>>>>>>> check this variable in the client side the value is null....
>>>>>>>
>>>>>>> What could be wrong?
>>>>>>>
>>>>>>> Thanks in advance, Santiago.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> -- 
>>>>>> View this message in context:
>>>>>> http://old.nabble.com/Object-not-modified-in-webservice-response---servicemix-4-tp27851039p27852567.html
>>>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Freeman Fang
>>>>> ------------------------
>>>>> Open Source SOA: http://fusesource.com
>>>>>
>>>>>
>>>>>
>>>>
>>>> -- 
>>>> View this message in context:
>>>> http://old.nabble.com/Object-not-modified-in-webservice-response---servicemix-4-tp27851039p27862696.html
>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>
>>> 
>>> 
>>> -- 
>>> Freeman Fang
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>> 
>>> 
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Object-not-modified-in-webservice-response---servicemix-4-tp27851039p27874516.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to