Howto adjust value for wsa:Action?
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Howto adjust value for wsa:Action?
by crapp
::
Rate this Message:
Hello,
Our consumer receives WS-Notifications via Muse and Axis2. The producer sends the notifications with the wsa:action attribute set to 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify' Our MUSE implementation currently listens for the wsa:action set to 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest'. I saw that in the WSDL and in the services.xml this wsa:action needs to be set. I did that, re-generated the sources of the client from WSDL and compiled them. Now I am getting the below error on my consumer. What else do I need to do to change the wsa:action attribute value on the consumer side?a INFO: There was an error while processing a request: [ID = 'NoMessageContent'] The NotificationMessage XML does not have a Message element. All messages must have a message payload associated with them. org.apache.muse.ws.notification.impl.SimpleNotificationMessage.<init>(SimpleNotificationMess age.java:117) org.apache.muse.ws.notification.impl.NotificationMessageSerializer.fromXML(NotificationMessa geSerializer.java:46) org.apache.muse.core.serializer.ArraySerializer.fromXML(ArraySerializer.java:126) org.apache.muse.core.routing.ReflectionMessageHandler.fromXML(ReflectionMessageHandler.java: 132) org.apache.muse.core.SimpleResource.invoke(SimpleResource.java:368) org.apache.muse.core.routing.SimpleResourceRouter.invoke(SimpleResourceRouter.java:290) org.apache.muse.core.platform.axis2.AxisIsolationLayer.invoke(AxisIsolationLayer.java:136) org.apache.muse.core.platform.axis2.AxisIsolationLayer.handleRequest(AxisIsolationLayer.java :88) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessage Receiver.java:88) org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessage Receiver.java:39) org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) 18 more... ------------------------------------------ Regards, Christian Rapp |
|
|
RE: Howto adjust value for wsa:Action?
by Vinh Nguyen (vinguye2)
::
Rate this Message:
Hi,
Can you paste the notification XML trace received by your client? The error indicates that the required <NotificationMessage> child element is not found. Also, are you trying to have your producer send a custom wsa:Action value other than the ".../NotifyRequest" one sent by Muse, or have your consumer handle a custom wsa:Action value? -Vinh -----Original Message----- From: crapp [mailto:christian.rapp@...] Sent: Tuesday, June 10, 2008 12:52 AM To: muse-user@... Subject: Howto adjust value for wsa:Action? Hello, Our consumer receives WS-Notifications via Muse and Axis2. The producer sends the notifications with the wsa:action attribute set to 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify' Our MUSE implementation currently listens for the wsa:action set to 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest' . I saw that in the WSDL and in the services.xml this wsa:action needs to be set. I did that, re-generated the sources of the client from WSDL and compiled them. Now I am getting the below error on my consumer. What else do I need to do to change the wsa:action attribute value on the consumer side?a INFO: There was an error while processing a request: [ID = 'NoMessageContent'] The NotificationMessage XML does not have a Message element. All messages must have a message payload associated with them. org.apache.muse.ws.notification.impl.SimpleNotificationMessage.<init>(Si mpleNotificationMess age.java:117) org.apache.muse.ws.notification.impl.NotificationMessageSerializer.fromX ML(NotificationMessa geSerializer.java:46) org.apache.muse.core.serializer.ArraySerializer.fromXML(ArraySerializer. java:126) org.apache.muse.core.routing.ReflectionMessageHandler.fromXML(Reflection MessageHandler.java: 132) org.apache.muse.core.SimpleResource.invoke(SimpleResource.java:368) org.apache.muse.core.routing.SimpleResourceRouter.invoke(SimpleResourceR outer.java:290) org.apache.muse.core.platform.axis2.AxisIsolationLayer.invoke(AxisIsolat ionLayer.java:136) org.apache.muse.core.platform.axis2.AxisIsolationLayer.handleRequest(Axi sIsolationLayer.java :88) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogi c(RawXMLINOutMessage Receiver.java:88) org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Abst ractInOutSyncMessage Receiver.java:39) org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) 18 more... ------------------------------------------ Regards, Christian Rapp -- View this message in context: http://www.nabble.com/Howto-adjust-value-for-wsa%3AAction--tp17749755p17 749755.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... |
|
|
Re: Howto adjust value for wsa:Action?
by crapp
::
Rate this Message:
Hello,
The WS-Notification standard states the wsa:Action attribute must be set to 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify'. As of this we can not change the client which sends it correctly. I resolved the problem by overwriting the class NotifyHandler and call the super constructor with the correct action uri. public class NotifyHandler extends AbstractMessageHandler { // // Response message never changes, so we use a static value // private static final Element _NOTIFY_RESPONSE = XmlUtils .createElement(WsnConstants.NOTIFY_RESPONSE_QNAME); public NotifyHandler() { super(WsnConstants.CONSUMER_URI + "/Notify", WsnConstants.NOTIFY_QNAME); } ...
|
|
|
RE: Howto adjust value for wsa:Action?
by Vinh Nguyen (vinguye2)
::
Rate this Message:
Hi Christian,
You're correct. The v1.3 spec does state that the Notify wsa:Action should be as you specified below. Please open a bug so that this can be fixed. -Vinh -----Original Message----- From: crapp [mailto:christian.rapp@...] Sent: Tuesday, June 10, 2008 10:43 PM To: muse-user@... Subject: Re: Howto adjust value for wsa:Action? Hello, The WS-Notification standard states the wsa:Action attribute must be set to 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify'. As of this we can not change the client which sends it correctly. I resolved the problem by overwriting the class NotifyHandler and call the super constructor with the correct action uri. public class NotifyHandler extends AbstractMessageHandler { // // Response message never changes, so we use a static value // private static final Element _NOTIFY_RESPONSE = XmlUtils .createElement(WsnConstants.NOTIFY_RESPONSE_QNAME); public NotifyHandler() { super(WsnConstants.CONSUMER_URI + "/Notify", WsnConstants.NOTIFY_QNAME); } ... crapp wrote: > > Hello, > > Our consumer receives WS-Notifications via Muse and Axis2. The > producer sends the notifications with the wsa:action attribute set to > 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify' > > Our MUSE implementation currently listens for the wsa:action set to > 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest' . > > I saw that in the WSDL and in the services.xml this wsa:action needs > to be set. I did that, re-generated the sources of the client from > WSDL and compiled them. Now I am getting the below error on my > consumer. What else do I need to do to change the wsa:action attribute > value on the consumer side?a > > INFO: There was an error while processing a request: > > [ID = 'NoMessageContent'] The NotificationMessage XML does not have a > Message element. All messages must have a message payload associated > with them. > > > org.apache.muse.ws.notification.impl.SimpleNotificationMessage.<init>( > SimpleNotificationMess > age.java:117) > > org.apache.muse.ws.notification.impl.NotificationMessageSerializer.fro > mXML(NotificationMessa > geSerializer.java:46) > > org.apache.muse.core.serializer.ArraySerializer.fromXML(ArraySerialize > r.java:126) > > MessageHandler.java: > 132) > > org.apache.muse.core.SimpleResource.invoke(SimpleResource.java:368) > > org.apache.muse.core.routing.SimpleResourceRouter.invoke(SimpleResourc > eRouter.java:290) > > org.apache.muse.core.platform.axis2.AxisIsolationLayer.invoke(AxisIsol > ationLayer.java:136) > > org.apache.muse.core.platform.axis2.AxisIsolationLayer.handleRequest(A > xisIsolationLayer.java > :88) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > ava:39) > > Impl.java:25) > java.lang.reflect.Method.invoke(Method.java:597) > > org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLo > gic(RawXMLINOutMessage > Receiver.java:88) > > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Ab > stractInOutSyncMessage > Receiver.java:39) > > 18 more... > ------------------------------------------ > > > Regards, > Christian Rapp > -- View this message in context: http://www.nabble.com/Howto-adjust-value-for-wsa%3AAction--tp17749755p17 770458.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... |
|
|
Re: Howto adjust value for wsa:Action?
by crapp
::
Rate this Message:
Opened up a bug in Jira for Muse: https://issues.apache.org/jira/browse/MUSE-289
|
|
|
class loading problem
by Scandelli Francesco
::
Rate this Message:
Hi all
I'm using some web-applications based on Muse 2.2.0 and Axis2 and deployed on Tomcat 5.5.x. Since I would like to deploy all Muse 2.2.0 and Axis2 jars (and also other libraries shared among the webapps) in only place, I tried to move them in shared/lib but I got some strange run-time classloader-related behaviours: classes not found and resources not found (like muse.xml). I made a lot of attempts trying to move different sets of jars and I individuated the following working configurations: - every Muse 2.2.0 and Axis2 jars in shared/lib except muse-platform-axis2-2.2.0.jar - every Muse 2.2.0 and Axis2 jars locally in WEB-INF/lib plus all the other jars containing classes referenced in muse.xml The same considerations are valid for the mini servlet deployment with the difference that the required jar is muse-platform-mini-2.2.0.jar. Has anyone else had my same problem? I think this should be written in Muse 2.2.0 documentation. Cheers Francesco -----Messaggio originale----- Da: crapp [mailto:christian.rapp@...] Inviato: gio 12/06/2008 7.37 A: muse-user@... Oggetto: Re: Howto adjust value for wsa:Action? Opened up a bug in Jira for Muse: https://issues.apache.org/jira/browse/MUSE-289 crapp wrote: > > Hello, > > Our consumer receives WS-Notifications via Muse and Axis2. The producer > sends the notifications with the wsa:action attribute set to > 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify' > > Our MUSE implementation currently listens for the wsa:action set to > 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest'. > > I saw that in the WSDL and in the services.xml this wsa:action needs to be > set. I did that, re-generated the sources of the client from WSDL and > compiled them. Now I am getting the below error on my consumer. What else > do I need to do to change the wsa:action attribute value on the consumer > side?a > > INFO: There was an error while processing a request: > > [ID = 'NoMessageContent'] The NotificationMessage XML does not have a > Message element. All messages > must have a message payload associated with them. > > > org.apache.muse.ws.notification.impl.SimpleNotificationMessage.<init>(SimpleNotificationMess > age.java:117) > > org.apache.muse.ws.notification.impl.NotificationMessageSerializer.fromXML(NotificationMessa > geSerializer.java:46) > > org.apache.muse.core.serializer.ArraySerializer.fromXML(ArraySerializer.java:126) > > org.apache.muse.core.routing.ReflectionMessageHandler.fromXML(ReflectionMessageHandler.java: > 132) > > org.apache.muse.core.SimpleResource.invoke(SimpleResource.java:368) > > org.apache.muse.core.routing.SimpleResourceRouter.invoke(SimpleResourceRouter.java:290) > > org.apache.muse.core.platform.axis2.AxisIsolationLayer.invoke(AxisIsolationLayer.java:136) > > org.apache.muse.core.platform.axis2.AxisIsolationLayer.handleRequest(AxisIsolationLayer.java > :88) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > java.lang.reflect.Method.invoke(Method.java:597) > > org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessage > Receiver.java:88) > > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessage > Receiver.java:39) > org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493) > 18 more... > ------------------------------------------ > > > Regards, > Christian Rapp > View this message in context: http://www.nabble.com/Howto-adjust-value-for-wsa%3AAction--tp17749755p17792832.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... Internet Email Confidentiality Footer ----------------------------------------------------------------------------------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. ----------------------------------------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... |
|
|
RE: class loading problem
by Chris.Twiner
::
Rate this Message:
Hi Francesco,
I would advise against this general approach of using shared/lib or common/lib etc. I understand the motivation but unless all of your tomcat web apps are deployed as a single unit you are introducing a direct jar coupling to all of your projects on single versions of the jars. From painful experience (that led me to use osgi for the majority of my new large projects) this will cause problems in the future in the form of jar / class path hell. You have seen a small part of that, but more difficult problems will follow. These unfortunately aren't wierd classloader problems, they are just part of the normal classloader problems that you have when you mix classloaders. I don't reasonably expect any project that uses a classloading / plugin system to work reliably at 100% of functionality except in the normal expected WEB-INF/lib fashion with a single classloader being used. cheers, Chris -----Original Message----- From: Scandelli Francesco [mailto:Francesco.Scandelli@...] Sent: Saturday, June 14, 2008 2:30 PM To: muse-user@... Subject: class loading problem Hi all I'm using some web-applications based on Muse 2.2.0 and Axis2 and deployed on Tomcat 5.5.x. Since I would like to deploy all Muse 2.2.0 and Axis2 jars (and also other libraries shared among the webapps) in only place, I tried to move them in shared/lib but I got some strange run-time classloader-related behaviours: classes not found and resources not found (like muse.xml). I made a lot of attempts trying to move different sets of jars and I individuated the following working configurations: - every Muse 2.2.0 and Axis2 jars in shared/lib except muse-platform-axis2-2.2.0.jar - every Muse 2.2.0 and Axis2 jars locally in WEB-INF/lib plus all the other jars containing classes referenced in muse.xml The same considerations are valid for the mini servlet deployment with the difference that the required jar is muse-platform-mini-2.2.0.jar. Has anyone else had my same problem? I think this should be written in Muse 2.2.0 documentation. Cheers Francesco -----Messaggio originale----- Da: crapp [mailto:christian.rapp@...] Inviato: gio 12/06/2008 7.37 A: muse-user@... Oggetto: Re: Howto adjust value for wsa:Action? Opened up a bug in Jira for Muse: https://issues.apache.org/jira/browse/MUSE-289 crapp wrote: > > Hello, > > Our consumer receives WS-Notifications via Muse and Axis2. The > producer sends the notifications with the wsa:action attribute set to > 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify' > > Our MUSE implementation currently listens for the wsa:action set to > 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/NotifyRequest' . > > I saw that in the WSDL and in the services.xml this wsa:action needs > to be set. I did that, re-generated the sources of the client from > WSDL and compiled them. Now I am getting the below error on my > consumer. What else do I need to do to change the wsa:action attribute > value on the consumer side?a > > INFO: There was an error while processing a request: > > [ID = 'NoMessageContent'] The NotificationMessage XML does not have a > Message element. All messages must have a message payload associated > with them. > > > org.apache.muse.ws.notification.impl.SimpleNotificationMessage.<init>( > SimpleNotificationMess > age.java:117) > > org.apache.muse.ws.notification.impl.NotificationMessageSerializer.fro > mXML(NotificationMessa > geSerializer.java:46) > > org.apache.muse.core.serializer.ArraySerializer.fromXML(ArraySerialize > r.java:126) > > MessageHandler.java: > 132) > > org.apache.muse.core.SimpleResource.invoke(SimpleResource.java:368) > > org.apache.muse.core.routing.SimpleResourceRouter.invoke(SimpleResourc > eRouter.java:290) > > org.apache.muse.core.platform.axis2.AxisIsolationLayer.invoke(AxisIsol > ationLayer.java:136) > > org.apache.muse.core.platform.axis2.AxisIsolationLayer.handleRequest(A > xisIsolationLayer.java > :88) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j > ava:39) > > Impl.java:25) > java.lang.reflect.Method.invoke(Method.java:597) > > org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLo > gic(RawXMLINOutMessage > Receiver.java:88) > > org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(Ab > stractInOutSyncMessage > Receiver.java:39) > > 18 more... > ------------------------------------------ > > > Regards, > Christian Rapp > -- View this message in context: http://www.nabble.com/Howto-adjust-value-for-wsa%3AAction--tp17749755p17 792832.html Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... Internet Email Confidentiality Footer ------------------------------------------------------------------------ ----------------------------- La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge (art. 616 C.P., D.Lgs n. 196/2003 Codice in materia di protezione dei dati personali). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. ------------------------------------------------------------------------ ----------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: muse-user-unsubscribe@... For additional commands, e-mail: muse-user-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
