Ruwan,

I've noticed that there is an encoding problem in the received response. The
response is encoded as UTF-8, but it contains accented characters: "é". I
would like to verify if the response sent by the webservice is correctly
encoded, but although I've activated log4j.category.httpclient.wire=TRACE
the request/response passing on the wire is not logged. How can these
messages be logged ?

If the response is correctly encoded - i.e. ISO-8859-1 - is there a way to
change the encoding in the ESB configuration ?

Regards, Stefan.


stlecho wrote:
> 
> Ruwan,
> 
> I've been re-configuring v1.7.1 and was able to call the webservice, but
> I'm still receiving an "Error in converting SOAP Envelope to Document"
> error message :o(.
> 
> Stacktrace:
> 2008-08-26 08:46:02,896 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> MESSAGE *********************** RampartReceiver received 
> <?xml version='1.0' encoding='utf-8'?><SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";><SOAP-ENV:Body>
> <ns:findPersonResponse
> xmlns:ns="urn://fsb.belgium.be/fphp/v3_0"><per:personList
> xmlns:per="urn://fsb.belgium.be/fphp/v3_0/person"
> xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
> xmlns="urn://fsb.belgium.be/fphp/v3_0/query" release="2008072901"
> time="2008-08-26T08:46:02.231+02:00" version="1.0"><per:context
> version="1.0"><ns0:client
> xmlns:ns0="urn://fsb.belgium.be/fphp/v3_0/context"><ns0:nationalNumber>63080214114</ns0:nationalNumber><ns0:enterpriseNumber>0477430931</ns0:enterpriseNumber><ns0:eid
> /><ns0:callerId>211011</ns0:callerId><ns0:language>fr</ns0:language></ns0:client><ns0:message
> xmlns:ns0="urn://fsb.belgium.be/fphp/v3_0/context"><ns0:messageId>FPHP-C5A86B63-C34A-428A-A425-8DE5AD791134</ns0:messageId><ns0:correlationId>FPHP-C5A86B63-C34A-428A-A425-8DE5AD791134</ns0:correlationId></ns0:message><ns0:application
> xmlns:ns0="urn://fsb.belgium.be/fphp/v3_0/context"><ns0:application>enot-fphp</ns0:application></ns0:application></per:context><per:searchCriteria
> version="1.0"><ns0:registers
> xmlns:ns0="urn://fsb.belgium.be/fphp/v3_0/searchcriteria"><ns0:register>RN</ns0:register><ns0:register>RR</ns0:register></ns0:registers><ns0:searchByNumber
> xmlns:ns0="urn://fsb.belgium.be/fphp/v3_0/searchcriteria"
> version="1.0"><ns0:number>19031319331</ns0:number></ns0:searchByNumber></per:searchCriteria><per:searchFilterName>all</per:searchFilterName><per:person
> version="1.0"><per:summary version="1.3"><sum:source
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">RN</sum:source><sum:number
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">19031319331</sum:number><sum:status
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">0</sum:status><sum:gender
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">1</sum:gender><sum:lastName
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">Sermon</sum:lastName><sum:firstName
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">Jules</sum:firstName><sum:birthDate
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary"><com:century
> xmlns:com="urn://fsb.belgium.be/fphp/v3_0/common">19</com:century><com:year
> xmlns:com="urn://fsb.belgium.be/fphp/v3_0/common">19</com:year><com:month
> xmlns:com="urn://fsb.belgium.be/fphp/v3_0/common">03</com:month><com:day
> xmlns:com="urn://fsb.belgium.be/fphp/v3_0/common">13</com:day></sum:birthDate><sum:birth_place_nis_code
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">23077</sum:birth_place_nis_code><sum:birth_place_description
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">Sint-Pieters-Leeuw</sum:birth_place_description><sum:nationality_code
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">BE</sum:nationality_code><sum:isAlive
> xmlns:sum="urn://fsb.belgium.be/fphp/v3_0/summary">false</sum:isAlive></per:summary><per:details><per:details_rr_rn><per:it000
> Type="000" Structure="A1"><rn2:NationalNumber
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:NationalNumber>19031319331</rn2:NationalNumber><rn2:Date><rn2:Century>19</rn2:Century><rn2:Year>19</rn2:Year><rn2:Month>03</rn2:Month><rn2:Day>13</rn2:Day></rn2:Date><rn2:Sex>1</rn2:Sex></rn2:NationalNumber></per:it000><per:it001
> Type="001" Structure="A1"><rn2:Date
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Century>19</rn2:Century><rn2:Year>82</rn2:Year><rn2:Month>06</rn2:Month><rn2:Day>19</rn2:Day></rn2:Date><rn2:Residence
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Code>99990</rn2:Code><rn2:Label>Décédé(e)</rn2:Label></rn2:Residence><rn2:Fusion
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";>0</rn2:Fusion><rn2:Language
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";>1</rn2:Language></per:it001><per:it001
> Type="001" Structure="A1"><rn2:Date
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Century>19</rn2:Century><rn2:Year>19</rn2:Year><rn2:Month>03</rn2:Month><rn2:Day>13</rn2:Day></rn2:Date><rn2:Residence
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Code>23077</rn2:Code><rn2:Label>Sint-Pieters-Leeuw</rn2:Label></rn2:Residence><rn2:Fusion
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";>0</rn2:Fusion><rn2:Language
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";>1</rn2:Language></per:it001><per:it010
> Type="010" Structure="A1"><rn2:Date
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Century>19</rn2:Century><rn2:Year>19</rn2:Year><rn2:Month>03</rn2:Month><rn2:Day>13</rn2:Day></rn2:Date><rn2:Name
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:LastName><rn2:Code>10568251</rn2:Code><rn2:Label>Sermon</rn2:Label></rn2:LastName><rn2:FirstName><rn2:Code>00020013</rn2:Code><rn2:Label>Jules</rn2:Label></rn2:FirstName></rn2:Name></per:it010><per:it020
> Type="020" Structure="A1"><rn2:Date
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Century>19</rn2:Century><rn2:Year>19</rn2:Year><rn2:Month>03</rn2:Month><rn2:Day>13</rn2:Day></rn2:Date><rn2:Address
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:ZipCode>1600</rn2:ZipCode><rn2:Street><rn2:Code>16000056</rn2:Code><rn2:Label>Georges
> Hensmansstraat</rn2:Label></rn2:Street><rn2:HouseNumber>16</rn2:HouseNumber></rn2:Address></per:it020><per:it031
> Type="031" Structure="B1"><rn2:Date
> xmlns:rn2="http://www.ibz.rrn.fgov.be/XSD/xm25/rn25Schema";><rn2:Century>19</rn2:Century></rn2:Date></per:it031></per:details_rr_rn></per:details></per:person></per:personList></ns:findPersonResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
> 2008-08-26 08:46:02,896 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> RampartEngine Enter process(MessageContext msgCtx)
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext ==================
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext  Property set on object
> [EMAIL PROTECTED]
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext   Key =SECURITY_VALIDATION_FAILURE
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext   Value Class = java.lang.Boolean
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext   Value Classloader = null
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext Call Stack = DEBUG_FRAME =
> org.apache.axis2.util.JavaUtils.callStackToString(JavaUtils.java:564)
>       DEBUG_FRAME =
> org.apache.axis2.context.AbstractContext.debugPropertySet(AbstractContext.java:416)
>       DEBUG_FRAME =
> org.apache.axis2.context.AbstractContext.setProperty(AbstractContext.java:182)
>       DEBUG_FRAME =
> org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:160)
>       DEBUG_FRAME =
> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
>       DEBUG_FRAME = org.apache.axis2.engine.Phase.invoke(Phase.java:317)
>       DEBUG_FRAME =
> org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
>       DEBUG_FRAME =
> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
>       DEBUG_FRAME =
> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:200)
>       DEBUG_FRAME =
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>       DEBUG_FRAME =
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>       DEBUG_FRAME = java.lang.Thread.run(Thread.java:595)
> 
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] DEBUG
> AbstractContext ==================
> 2008-08-26 08:46:02,928 [192.168.13.175-INFOR2] [HttpClientWorker-1] ERROR
> AxisEngine Error in extracting message properties
> org.apache.axis2.AxisFault: Error in extracting message properties
>       at
> org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166)
>       at
> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
>       at org.apache.axis2.engine.Phase.invoke(Phase.java:317)
>       at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)
>       at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)
>       at
> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:200)
>       at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>       at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>       at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.rampart.RampartException: Error in extracting
> message properties
>       at
> org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:356)
>       at org.apache.rampart.RampartEngine.process(RampartEngine.java:70)
>       at
> org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
>       ... 7 more
> Caused by: org.apache.ws.security.WSSecurityException: Error in converting
> SOAP Envelope to Document; nested exception is: 
>       org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxEOFException:
> Unexpected EOF; was expecting a close tag for element <rn2:Century>
>  at [row,col {unknown-source}]: [4,5335]
>       at
> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:161)
>       at
> org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:162)
>       ... 9 more
> Caused by: org.apache.axiom.om.OMException:
> com.ctc.wstx.exc.WstxEOFException: Unexpected EOF; was expecting a close
> tag for element <rn2:Century>
>  at [row,col {unknown-source}]: [4,5335]
>       at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:249)
>       at org.apache.axiom.om.impl.llom.OMNodeImpl.build(OMNodeImpl.java:327)
>       at
> org.apache.axiom.om.impl.llom.OMElementImpl.build(OMElementImpl.java:706)
>       at
> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:96)
>       ... 10 more
> Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF; was
> expecting a close tag for element <rn2:Century>
>  at [row,col {unknown-source}]: [4,5335]
>       at
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
>       at
> com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2730)
>       at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
>       at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:506)
>       at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:161)
>       ... 13 more
> 
> 
> Regards, Stefan.
> 
> 
> Ruwan Linton-3 wrote:
>> 
>> stlecho wrote:
>>> Ruwan,
>>>
>>> I've been adding my endpoints and proxies to v1.7.1. When sending an XML
>>> request to the proxy endpoint, I'm receiving a "HTTP/1.1 202 Accepted"
>>> response but I have the impression that the external webservice is not
>>> called. 
>>>
>>> Comparing the old (v1.7beta2) with the new synapse.xml config file, I've
>>> noticed that it was possible to specify an endpoint on the target
>>> element.
>>> Is this still supported in v1.7.1 ?
>>>   
>> Yeah, it does. Basically you should be able to export the full 
>> configuration of the ESB 1.7 to the 1.7.1.
>> 
>> May be you are invoking the proxy with a wrong URL in which case the 
>> main sequence is used for mediation and drops the message.
>> 
>> Thanks,
>> Ruwan
>>> Regards, Stefan.
>>>
>>> Ruwan Linton-3 wrote:
>>>   
>>>> Hi Stefan,
>>>>
>>>> We didn't fixed any functional issues in the 1.7.1 release, but we just 
>>>> fixed the FireFox3 issues which are on the UI layer. Being said that 
>>>> this feature is there on the 1.7 release as well. There fore this has
>>>> to 
>>>> work if the configuration is correct, so you may give this a try with 
>>>> the new release and see whether you can get this to work.... If there 
>>>> are any errors, you can raise them on them and I will help you to get 
>>>> these issues resolved.
>>>>
>>>> Thanks,
>>>> Ruwan
>>>>
>>>> stlecho wrote:
>>>>     
>>>>> Ruwan,
>>>>>
>>>>> Has this functionality been released in the v1.7.1 ?
>>>>>
>>>>> PS: Sorry for this terrible late response, but I had some other
>>>>> priorities.
>>>>>
>>>>> Regards, Stefan.
>>>>>
>>>>> Ruwan Linton-3 wrote:
>>>>>   
>>>>>       
>>>>>> stlecho wrote:
>>>>>>     
>>>>>>         
>>>>>>> The response I'm getting back from the Webservice is not signed with
>>>>>>> WS-Security. If Rampart tries to treat this message in raises an
>>>>>>> exception,
>>>>>>> because it is supposed to handle signed messages. Rampart should in
>>>>>>> this
>>>>>>> case not be activated at all.
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>> Hi Stefan,
>>>>>>
>>>>>> Sorry for the late reply, I just did another test on this
>>>>>> functionality 
>>>>>> and found that it is working on the SNAPSHOT (latest build). Could
>>>>>> you 
>>>>>> please bring the summery of the problem with all logs and
>>>>>> configurations 
>>>>>> in to the table and lets try to get this resolved.
>>>>>>
>>>>>> You may send a mail to the user list or file a JIRA issue with all
>>>>>> the 
>>>>>> relevant configurations to reproduce the issue.
>>>>>>
>>>>>> Thanks,
>>>>>> Ruwan
>>>>>>
>>>>>> _______________________________________________
>>>>>> Esb-java-user mailing list
>>>>>> [email protected]
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>>>>
>>>>>>
>>>>>>     
>>>>>>         
>>>>>   
>>>>>       
>>>> _______________________________________________
>>>> Esb-java-user mailing list
>>>> [email protected]
>>>> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>>>
>>>>
>>>>     
>>>
>>>   
>> 
>> 
>> _______________________________________________
>> Esb-java-user mailing list
>> [email protected]
>> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WSSecurityException%3A-Error-in-converting-SOAP-Envelope-to-Document-tp18058906p19157007.html
Sent from the WSO2 ESB Users mailing list archive at Nabble.com.


_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to