One scenario where this exception might help is when the user mistakenly tries to engage two different versions of the same module, assuming that the exception is given based on the ModuleName (not Name+Version).
For example axis2.xml may engage one verison and the client code may engage another.
it will be very difficult to find out what went wrong, without this exception.
Chamikara
On 5/14/06, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
Hi all,Bringing the following issue to your attention again..> To Jaliya:
> if you are getting "Trying to engage a module which is already
> engaged". , then you are trying to do the same thing as exception says ,
> if you try to engage a module which is already engaged we are throwing
> exception :)
>I'm facing some serious problems Kandula test cases regarding the above issue.. I was not able to recall the same operation in a stub withing the same test case from two different methods.. It always gives the "Trying to engage a module which is already
engaged" exception.IMO there aren't any need to throw an Exception here.. Module user wants it to be engaged any way.. I don't see any probs if it gets engaged twice, if it make sure to keep engaged.. This deserves only a *warning*... Please explain If there are any serious consequences that can arise due to engaging a module twice...With my experience the trickiest part when doing some serious stuff with axis2 is engaging modules and mentioning repositories.. I don't want to see the above exception coming out from no where after I have wasted huge amount of sweat to get it engaged...Any comments...~Thilina---------- Forwarded message ----------
From: Thilina Gunarathne < [EMAIL PROTECTED]>
Date: Mar 27, 2006 2:18 PM
Subject: Re: [Axis2] WS-Addressing headers are missing from the SOAP message
To: [email protected]
Do we really need to throw an exception in this case.. IMHO it should
be just a warning.. Not an exception.. Whether it happened once or
twice, what the user wants is module to be engaged.....
~Thilina
On 3/24/06, Deepal Jayasinghe < [EMAIL PROTECTED]> wrote:
> hmm ,
> you have to engage addressing in both client side and server side.
> and if you engage addressing in the client side , if you want addressing
> you have to send the action
> [ option.setAction("ANY-URI") ]
>
> To Jaliya:
> if you are getting "Trying to engage a module which is already
> engaged". , then you are trying to do the same thing as exception says ,
> if you try to engage a module which is already engaged we are throwing
> exception :)
>
>
> Rajith Attapattu wrote:
>
> > 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* < [EMAIL PROTECTED]
> > <mailto: [EMAIL PROTECTED]>> 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" < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>>
> > To: < [email protected] <mailto: [email protected]>>
> > 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~
> > >
> > >
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
