Hi, you can't add Rampart. You can only add it to the inflow of Muse, as Muse then uses the Axis2 Inflow. So in each case you have to use the Axis2 engine (as Rampart is an Axis2 module).
For the outgoing flow Muse uses a low-level http call and does not use Axis2. So there is no way to use Rampart for the outgoing flow. What I did, was to add a security header to the Muse header and so extended some classes. With this you get a SOAP message with the WSSE header and the incoming Axis2 Engine, with Rampart, does the rest (I think I posted a solution in the middle of the year to this mailing list). Hopes this helps. @Alfredo: Please use the muse mailing list. Best regards, Matthias -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 4. Dezember 2007 15:38 An: Beil, Matthias Betreff: Rampart handling faults Hi Beil! Im making a WS-NotificationBroker on my own and i decided to implement it on Apache MUSE and i did it rigth. ( i think so ) I can send notifications and subscribe consumers wich will be notified when the broker receives a notificacion. It all works. Now im in the way to add security to it and i decided to use wss4j but the API seems to hard to work with that i decided to go for help and use rampart. Here comes the problem: I made my muse api using wsdl2java.sh -j2ee axis2 -wsdl broker.wsdl ( on previous versions i did mini instead of axis2 but this wouldnt be a problem ... i think ) so the axis2 server muse gives me is not the war archive i can upload to tomcat wich includes rampart. I've tried to add the libraries of rampart to my muse app but it allways crash when i try to access the axis2 homepage. Could you tell me how to integrate muse and rampart? if so, what actions of rampart do you think are useful for WS-Notification? Thanks a lot for your time beil wrote: > > 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 > > > > > Quoted from: http://www.nabble.com/Rampart-handling-faults-tf3601253s12049.html#a10059532 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
