Hmm, I wouldn't go as far to say that Muse is non-compliant with WS-N 1.3. Muse's NotificationConsumer does meet the specification for the Notify message by handling the message properly. Just that it returns a response to the sender, which is extra behavior on top of the specification. I'm not sure this means non-compliance.
If you look at the last sentence on p.12 of the specification found via the link below, it just says that: "No response is expected from the NotificationConsumer upon receipt of this message." But it doesn't mean that the consumer can't return a response at all. In a way, I think returning a response is good because it lets the sender know that the notification was received successfully by the consumer. Perhaps Metro should just ignore the response if it knows an operation doesn't need a response. But then, it still needs to be smart enough to handle responses like an http 400 error:) http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-os.pdf -----Original Message----- From: Beil, Matthias [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 10, 2007 12:12 AM To: [email protected] Subject: AW: Notify returns a SOAP message Hi, it's true that Axis2 doesn't return a response by its own. As I'm using the Axis2 environment of Muse the incoming request goes through the in-engine of Axis2. The response returns through the out-engine. What I did was to add an Axis2 handler to this out flow. This handler just drops the response. With a bit more logic it would be possible to filter the returning messages. But this is not the solution: The problem lies within Muse himself! The "notify" message is defined as an "out-only" message (see wsn-ws_base_notification-1.3-spec-os line 363 and the wsdl file). This means that there is absolutely NO return value expected!!!! Neither a response, nor any fault message. But Muse doesn't implement this in this way. The implementation of Muse always returns a "NotifyResponse" and / or a fault message. But for the "notify" message, even a fault return is not expected. So it is Muse who does not comply with the WS-N 1.3 Specification! Regards, Matthias -----Ursprüngliche Nachricht----- Von: Vinh Nguyen (vinguye2) [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 9. Oktober 2007 20:38 An: [email protected] Betreff: RE: Notify returns a SOAP message I believe the response is coming from NotifyHandler, which is created by SimpleNotificationConsumer to handle the "notify" message. notifyHandler.toXML(Object) always returns a static xml response. This is where the fix needs to be made. I don't believe Axis2 itself is automatically returning a response. If it is, then you'd also get a response for all custom operations that don't have a return value, which then should be very noticable. -----Original Message----- From: beil [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 2:36 AM To: [email protected] Subject: Re: Notify returns a SOAP message Hi, I'm using the SimpleNotificationConsumer. Finally I gave up to find the source of this return response. The solution I finally used, was to create an abort handler. This is just a class, which aborts all response message in an Axis2 handler. Made an Axis2 handler out of it and added this handler to axis2.xml file. So no responses at all are returned from the wsn-consumer. In our environment I can live with this solution. THX for the help. Regards, Matthias Kam K. Yee wrote: > > Matthias, > > Are you using the SimpleNotificationConsumer default implementation or > did you write your own? > > > Regards, > Kam K. Yee > IBM Corporation > > > ----- Original Message ----- > From: "Beil, Matthias" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, September 19, 2007 6:00 AM > Subject: Notify returns a SOAP message > > > Hi, > > we need urgent help on an aspect that so far didn't make a problem, > but now does! > > In the WS-N specification the "notify" method is defined as an > out-only method. This means that no reply at all is expected. This is > the way how Metro implements this method. But Muse returns a result > SOAP message. As Metro can't interpret this message, they resend the > notification in a loop. > > As Muse is not conforming to the WS-N specification, is there any > possibility to avoid the returning of a SOAP message? > > I already tried to overwrite the AxisIsolationLayer class, but this > only resulted in the fact, that an empty body element was returned in > the SOAP message. Who creates the returned SOAP message? > > Would be great if someone could help quickly, as we need a solution > for going live with the system. > > Mit freundlichen Gruessen / With kind regards Matthias Beil > > > > > -- View this message in context: http://www.nabble.com/Notify-returns-a-SOAP-message-tf4479979.html#a1311 2206 Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
