Hello All, Following the advice below i created my own service having the arguments and returning element being an OMElement. However, what i want is to have the response to include the wsa:MessageId. How do i do this in the service? I need to return the soap:body so i can define the wsa header. Any ideas?
Thanks in advance. Kind regards, Erwin -----Oorspronkelijk bericht----- Van: Erwin Reinhoud Verzonden: dinsdag 9 oktober 2007 8:43 Aan: [email protected] Onderwerp: RE: axis2 1.3 wsa:MessageID not in generated service skeleton response Hello Deepal, We have to comply with a standard (governmental) that prescribes the use of a messageid in request/response. In case on application level the communbication is with jms the messages can be linked. Until now i have used the "contract first" principle to make a service, do i have to let that go now? How about that message below, i guess it will not be implemented? Thanks in advance. Kind regards, Erwin -----Oorspronkelijk bericht----- Van: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Verzonden: maandag 8 oktober 2007 17:23 Aan: [email protected] Onderwerp: Re: axis2 1.3 wsa:MessageID not in generated service skeleton response Erwin Reinhoud wrote: > Hello All, > > I generated a serviceskeleton with adb and enabled ws-addressing both > on service and client. In the response i don't see the MessageID. How > do you set your own messageID in the serviceskeleton code? In Axis2 1.3 you do not have a way to set the message ID when you use codegeneration (skel). In the meantime having a message id is not an mandatory , so may I know why do you want this message id ? Thanks Deepal > > > I found this message, but no related issue in jira: > http://mail-archives.apache.org/mod_mbox/ode-user/200707.mbox/[EMAIL > PROTECTED] > > Anybody know if there is an issue and how to set a certain value for > the wsa:messageid from the serviceskeleton? > > Thanks in advance. > > Kind regards, > > Erwin > > --------------------------------------------------------------------- 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]
