Rampart handling faults

[Beil, Matthias]

Hi,

 

I've integrated Rampart into Apache Muse deployed with Axis2. Everything
works ok, except for faults.

 

When I get a fault in Muse something like:

 

<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";

      xmlns:wsa="http://www.w3.org/2005/08/addressing";>

      <soapenv:Header>

 
<wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>

            <wsa:ReplyTo>

 
<wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address>

            </wsa:ReplyTo>

 
<wsa:MessageID>urn:uuid:59B76D47CA5BA7E4EF11745797877802</wsa:MessageID>

 
<wsa:Action>http://docs.oasis-open.org/wsn/bw-2/NotificationProducer/Get
CurrentMessageRequest</wsa:Action>

            <wsa:RelatesTo
wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>

                  uuid:c176cdf5-f8c7-e119-0a7f-996027c1d95a

            </wsa:RelatesTo>

      </soapenv:Header>

      <soapenv:Body>

            <soap:Fault
xmlns:soap="http://www.w3.org/2003/05/soap-envelope";

 
xmlns:tns="http://axis2.platform.core.muse.apache.org";>

                  <soap:Code>

                        <soap:Value>soap:Receiver</soap:Value>

                  </soap:Code>

                  <soap:Reason>

                        <soap:Text>

                             [ID = 'NoMessageAvailable'] The topic
'{http://java.sun.com/products/oss/xml/WsnOssj}vf-gsp' has not

                             published any messages.

                        </soap:Text>

                  </soap:Reason>

                  <soap:Detail>

                        <wsnt:NoCurrentMessageOnTopicFault
xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2";>

                             <wsrf-bf:Timestamp
xmlns:wsrf-bf="http://docs.oasis-open.org/wsrf/bf-2";>

                                   2007-03-22T17:09:53+01:00

                             </wsrf-bf:Timestamp>

                        </wsnt:NoCurrentMessageOnTopicFault>

                  </soap:Detail>

            </soap:Fault>

      </soapenv:Body>

</soapenv:Envelope>

 

I receive at the client (TCP/IP monitor) something like this:

 

<soapenv:Envelope

    xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";
xmlns:wsa="http://www.w3.org/2005/08/addressing";>

    <soapenv:Header>

        <wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>

        <wsa:ReplyTo>

 
<wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address>

        </wsa:ReplyTo>

 
<wsa:MessageID>urn:uuid:772847914BDD8FECF511769028104156</wsa:MessageID>

 
<wsa:Action>http://docs.oasis-open.org/wsn/bw-2/NotificationProducer/Get
CurrentMessageRequest</wsa:Action>

        <wsa:RelatesTo
wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>uuid:c
83275dc-acfe-a34c-97ed-0ba167ac51fa</wsa:RelatesTo>

    </soapenv:Header>

    <soapenv:Body>

        <soap:Fault xmlns:soap="http://www.w3.org/2003/05/soap-envelope";
xmlns:tns="http://axis2.platform.core.muse.apache.org";>

            <soap:Code>

                <soap:Value>soap:Receiver</soap:Value>

            </soap:Code>

            <soap:Reason/>

            <soap:Detail/>

        </soap:Fault>

    </soapenv:Body>

</soapenv:Envelope>

 

The reason and detail are gone. Muse returns the original fault in the
normal "Outflow" of Axis2, as a normal reply. I checked that the
original fault is send leaving Muse. Before I installed Rampart the
faults where transferred correctly.

 

This only happens for faults! For normal messages everything is okay.

 

What can I do, that faults go through correctly?

 

Mit freundlichen Gruessen / With kind regards

Matthias Beil