axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajith Attapattu" <rajit...@gmail.com>
Subject Re: [Axis2] WS-Addressing headers are missing from the SOAP message
Date Thu, 23 Mar 2006 22:33:28 GMT
Hi Deepal,

I still get the error. I doubled checked and verified I was on the latest
revision.
I did a clean build just to make sure.

So can you please verify and let me know. I still see the error in the log
files as "addressing disabled"

Regards,

Rajith

On 3/23/06, Jaliya Ekanayake <jnekanayake@gmail.com> wrote:
>
> I have also noticed something similar and also this.
>
> When I try to engage addressing using the client code it gives me the
> error
> saying
> "Trying to engage a module which is already engaged".
>
> Do we need to give this as an Exception?
> I feel that we should proceed normally if the user trying to engaged it
> again.
>
> - Jaliya
>
> ----- Original Message -----
> From: "Deepal Jayasinghe" <deepal@opensource.lk>
> To: <axis-dev@ws.apache.org>
> Sent: Wednesday, March 22, 2006 11:57 PM
> Subject: Re: [Axis2] WS-Addressing headers are missing from the SOAP
> message
>
>
> > Sorry there was a small mistake , but we fixed that :) , you wont get
> > such a behavior in 0.95
> >
> > and if you are going to use addressing , don't forget to put action else
> > you will be getting a nice exception :)
> >
> >
> > Rajith Attapattu wrote:
> >
> >> Hi All,
> >>
> >> I have enabled addressing in the axis2.xml
> >> And when checked from web console I see addressing module as engaged.
> >> Also the handler chain containes the addressing handlers.
> >> But I don't even see the "To" wsa header.
> >>
> >> However in the log I see the message addressing disabled.
> >>
> >> Can anybody tell me what I am missing?? or is there anything else to
> do?
> >>
> >> From a coding perspective this is what I wanted to do
> >>
> >>             EndpointReference ref = new EndpointReference(url);
> >>             ref.setName("ReplyTo");
> >>             ref.addReferenceParameter(new
> >> QName(AddressingConstants.WSA_DEFAULT_PREFIX,"sessionId"),sessionId);
> >>             msgContext.setReplyTo(ref);
> >>
> >> Anything missing??
> >>
> >> Regards,
> >>
> >> Rajith
> >
> >
> > --
> > Thanks,
> > Deepal
> > ................................................................
> > ~Future is Open~
> >
> >
>
>

Mime
View raw message