[ http://issues.apache.org/jira/browse/AXIS2-1801?page=all ]
Deepal Jayasinghe resolved AXIS2-1801.
--------------------------------------
Resolution: Won't Fix
SetOperationContext had threading issues so we had to remove that and we
provide some other way to get access to the contexts. So now inside you method
invocation you can get current message and from that u can get access to any of
the contexts.
So you want to access message context inside a method call "foo" then you can
do that as follows'
public String foo(){
MessageContext msg = MessageContext.getCurrentContext();
}
> setOperationContext not being invoked
> -------------------------------------
>
> Key: AXIS2-1801
> URL: http://issues.apache.org/jira/browse/AXIS2-1801
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.1
> Environment: JDK 1.5
> Tomcat 5.5 rampart 1.1
> Reporter: Gary Jacobs
> Priority: Minor
>
> I have a service that ran successfully under Axis 1.0 that had a
> setOperationContext method that was invoked by Axis prior to the operation
> method being invoked
> Since migrating to Axis 1.1 I find that this operation is no longer being
> invoked by access
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
