Hi Chris, Yes, I am using a TopicListener which is a NotificationMessageListener. Currently I am able to send back a SOAP-Fault, but that does not include sending back a HTTP500. It rather returns a HTTP200 which does not help us very much.
Is it possible to overwrite the class responsible for setting the HTTP returncode? Because we can not wait until the issue you mentioned has been fixed. Do you have the issue number of the mentioned issue? Regards, Christian -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. Juli 2008 14:47 An: [email protected] Betreff: RE: Responde with HTTP 500 on purpose Hi, Just to be sure are you receiving the message with a NotificationMessageListener? If so you can't actually throw anything back to the environment (there is a current JIRA for this I beleive) the Throwable will just be caught and logged. Using Axis2 directly (1.1 and above) the MessageContext.getCurrentMessageContext should allow you to directly set a soap fault for the reply, thus causing a 500. http://wso2.org/library/106 let us know how you get on cheers, Chris -----Original Message----- From: Rapp, Christian [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2008 1:59 PM To: [email protected] Subject: AW: Responde with HTTP 500 on purpose Hi, Muse runs on top of Axis2. Regards, Christian -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 3. Juli 2008 13:56 An: [email protected] Betreff: RE: Responde with HTTP 500 on purpose Hi Christian, which environment (isolation layer) are you using? As Muse is a plugable environment it does not directly interact with the HttpRequest or force return codes. As such it depends on the environment it runs in to make sensible decisions. cheers, Chris -----Original Message----- From: Rapp, Christian [mailto:[EMAIL PROTECTED] Sent: Thursday, July 03, 2008 1:45 PM To: [email protected] Subject: Responde with HTTP 500 on purpose Hello, We receive WS-Notifications from a server. We than try to store the notification first. If this fails, we need to send back a HTTP 500 errorcode so that the server knows, that we did not receive the notification successfully. Is there are a way in muse how we can accomplish that? Regards, Christian --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
