Re: "Invocation arguments were modified" exception in HandlerChainImpl class

[Kieran McPeake]

Hi - 

With Axis 1.2 when I try to modify a child within the
soap body using a client handler I am getting :
"java.lang.RuntimeException: Invocation arguments were
modified" exception at 
org.apache.axis.handlers.HandlerChainImpl.postInvoke(HandlerChainImpl.java:201)
This was I believe working okay with axis 1.1.
(Inserting and deleting child elements seems okay in
1.1. & 1.2)

I think I am experiencing a similar problem as
reported on 2005-03-22 by Timour Mouratov in msg :
Re: "Invocation arguments were modified" exception in
HandlerChainImpl class

I did not see any resolution to his question ?

I note that there was work done recently to
HandlerChainImp.java file - is that to fix this
problem ? 
See
http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/handlers/HandlerChainImpl.java?r1=1.18&r2=1.19

Cheers, 
Kieran





___ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail 
http://uk.messenger.yahoo.com

Re: "Invocation arguments were modified" exception in HandlerChainImpl class

[Timour Mouratov]

It's even more restricted, I can not modify (remove or replace) a soap
body child anywhere in rpc handler.

On Tue, 22 Mar 2005 11:26:19 -0500, Timour Mouratov <[EMAIL PROTECTED]> wrote:
> Hello,
> 
> We've started getting the following exception in axis 1.2RC2+:
> 
> java.lang.RuntimeException: Invocation arguments were modified
> at 
> org.apache.axis.handlers.HandlerChainImpl.postInvoke(HandlerChainImpl.java:201)
> at 
> org.apache.axis.handlers.HandlerChainImpl.handleRequest(HandlerChainImpl.java:154)
> 
> Some special(maintenance)  requests that come to axis service are
> blocked by our rpc handler. When handler catches special type of
> request  it _empties_ it and returns false from
> handleRequest(MessageContext context) method , and this is the moment
> when exception occurs.
> 
> I checked the CVS and found that modification were made to
> org.apache.axis.handlers.HandlerChainImpl (revision 1.16). There is if
> statement now in "postInvoke" method (line 199)  that checks cached
> value of jaxrpc method info with actual one. In our case they are not
> equal because our handler _emptied_  a message.
> 
> Is this is proper behaviour or a bug ?
> 
> Thanks.
> Timour
>