Hi,

hmm, actually the server should not return a SOAP fault at all for my
request, and it doesn't if I'm creating the request with CXF 3.0.5.

I've added a LoggingInInterceptor to catch the SOAP fault, here it is:

<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope";
xmlns:a="http://www.w3.org/2005/08/addressing";>
   <s:Header>
     <a:Action
s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
<a:RelatesTo>urn:uuid:af9c75b2-3d20-4bd3-a5b1-109d0d0e1d91</a:RelatesTo>
   </s:Header>
   <s:Body>
     <s:Fault>
       <s:Code>
         <s:Value
xmlns:a="http://mps.avs.abdata.aponet.de/faults";>a:Sender</s:Value>
       </s:Code>
       <s:Reason>
         <s:Text xml:lang="">Fehler-Code: R-206&#xD;
           Das zur Signierung der Daten verwendete Zertifikat ist
ungültig.&#xD;
           &#xD;
           Bitte wenden Sie sich unter Angabe des Fehler-Codes 'R-206'
an ihr Systemhaus.&#xD;
           &#xD;
           Fehler-Code: R-206
         </s:Text>
       </s:Reason>
     </s:Fault>
   </s:Body>
</s:Envelope>

"Das zur Signierung der Daten verwendete Zertifikat ist ungültig"
translates to "The certificate used for signing is not valid".

However, I'm sure it is valid. Seems like something in the signature got
broken from the 3.0 to the 3.1 series.


Best regards,
Stefan


Am 15.06.2015 um 13:25 schrieb Aki Yoshida:
> You are using soap 1.2. and soap 1.2 allows only one of the standard
> fault codes.
> http://www.w3.org/TR/soap12-part1/#faultcodes
> http://www.w3.org/TR/soap12-part1/#tabsoapfaultcodes
>
> If you were using soap 1.1, there should be no check so your custom
> code will get accepted.
> regards, aki
>
> 2015-06-15 12:53 GMT+02:00 Pröls, Stefan <[email protected]>:
>> Hello,
>>
>> I'm using JDK 1.8.0_45 on Linux with both CXF 3.0.5 and CXF 3.1.1.
>>
>>
>> Best regards,
>> Stefan
>>
>>
>> Am 15.06.2015 um 12:46 schrieb Aki Yoshida:
>>> which jdk version are you using?
>>> I think this has probably something to do with your jdk version.
>>>
>>>
>>> 2015-06-15 10:53 GMT+02:00 Pröls, Stefan <[email protected]>:
>>>> Hello,
>>>>
>>>> I'm having trouble upgrading my WebService-client from CXF 3.0.5 to 3.1.1.
>>>> It works very well with 3.0.5, but throws a
>>>>
>>>> java.lang.reflect.UndeclaredThrowableException
>>>>            at com.sun.proxy.$Proxy46.holeStatusReport(Unknown Source)
>>>>            at
>>>> de.pharmatechnik.apotheke.armin.ARMINImpl.holeStatusReport(ARMINImpl.java:348)
>>>> Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl:
>>>> {http://mps.avs.abdata.aponet.de/faults}Sender is not a standard Code value
>>>>            at
>>>> com.sun.xml.messaging.saaj.soap.ver1_2.Fault1_2Impl.checkIfStandardFaultCode(Fault1_2Impl.java:146)
>>>>            at
>>>> com.sun.xml.messaging.saaj.soap.impl.FaultImpl.setFaultCode(FaultImpl.java:139)
>>>>            at
>>>> com.sun.xml.messaging.saaj.soap.impl.FaultImpl.setFaultCode(FaultImpl.java:102)
>>>>            at
>>>> org.apache.cxf.binding.soap.saaj.SAAJUtils.setFaultCode(SAAJUtils.java:65)
>>>>            at
>>>> org.apache.cxf.jaxws.JaxWsClientProxy.createSoapFault(JaxWsClientProxy.java:229)
>>>>            at
>>>> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:157)
>>>>            ... 2 more
>>>>
>>>> with 3.1.1 and currently I don't really understand what's going wrong.
>>>>
>>>> This is the WSDL to the WebService my client tries to access:
>>>>
>>>> https://rheaavs.element44.net/AvsMpsService_R1_Variante2.wsdl
>>>>
>>>> Because of all the WS-Security stuff needed by the WS (Certificates and
>>>> Passwords) I cannot provide a working implementation for the client.
>>>>
>>>> However, maybe someone with a deeper knowledge of CXFs internals can
>>>> identify the cause of the problem from the logs. I've attached two
>>>> log-files for comparison. apache-3.0.5.log is a trace of a successful
>>>> Webservice-call with version 3.0.5, while apache-3.1.1.log logs a
>>>> failing call
>>>>     of the same WS-operation with 3.1.1.
>>>>
>>>>
>>>> Best regards,
>>>> Stefan
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> PHARMATECHNIK GmbH und Co. KG
>>>> Münchner Strasse 15
>>>> D-82319 Starnberg
>>>>
>>>> Sitz der Gesellschaft: Starnberg
>>>> HRA: 64434, HRB: 66369, Amtsgericht München
>>>> Geschäftsführer: Dr. Detlef Graessner, Cornelia Graessner-Neiss, Stephan 
>>>> Jörgens
>>
>> --
>> Mit freundlichen Grüßen
>>
>> Stefan Pröls
>> Entwicklung Systemintegration
>>
>> PHARMATECHNIK GmbH & Co. KG
>> Geschäftsstelle Passau, Neuburger Str. 128, 94036 Passau
>>
>> Tel.: +49 851 98865-205, Fax: +49 851 98865-199
>> [email protected], www.pharmatechnik.de
>>
>> ________________________________
>>
>> PHARMATECHNIK GmbH und Co. KG
>> Münchner Strasse 15
>> D-82319 Starnberg
>>
>> Sitz der Gesellschaft: Starnberg
>> HRA: 64434, HRB: 66369, Amtsgericht München
>> Geschäftsführer: Dr. Detlef Graessner, Cornelia Graessner-Neiss, Stephan 
>> Jörgens


--
Mit freundlichen Grüßen

Stefan Pröls
Entwicklung Systemintegration

PHARMATECHNIK GmbH & Co. KG
Geschäftsstelle Passau, Neuburger Str. 128, 94036 Passau

Tel.: +49 851 98865-205, Fax: +49 851 98865-199
[email protected], www.pharmatechnik.de

________________________________

PHARMATECHNIK GmbH und Co. KG
Münchner Strasse 15
D-82319 Starnberg

Sitz der Gesellschaft: Starnberg
HRA: 64434, HRB: 66369, Amtsgericht München
Geschäftsführer: Dr. Detlef Graessner, Cornelia Graessner-Neiss, Stephan Jörgens

Reply via email to