[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456985 ]
Glen Daniels commented on AXIS2-1823:
-
Sanjiva: I actually made it an instance var of the ServiceContext, because some
code paths through the stub objects don'
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456512 ]
Sanjiva Weerawarana commented on AXIS2-1823:
+1 for getLastOperationContext instead of getLastMC() as the latter is
relatively meaningless esp. if asyn
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456490 ]
Shaoguang Cong commented on AXIS2-1823:
---
Glen,
For the problem I try to resolve, all the proposed solutions here will work.
So you can decide which way is b
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456477 ]
Glen Daniels commented on AXIS2-1823:
-
Hey folks:
The rationale behind the switch to turn the cache on/off was that keeping a
reference to the OC in a live ob
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456470 ]
Shaoguang Cong commented on AXIS2-1823:
---
Glen, I'm playing with the released version 2.1.1. So I cannot check the fix
in the trunk.
>From purely a user's v
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456307 ]
Sanjiva Weerawarana commented on AXIS2-1823:
Do we really need setCachcingOperationContext()?? When I looked at it I didn't
think there would be any co
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456237 ]
Glen Daniels commented on AXIS2-1823:
-
This has been fixed on the trunk. The way this would work is as follows:
stub._getServiceClient().setCachingOperationCo
[
http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456178 ]
Deepal Jayasinghe commented on AXIS2-1823:
--
How about adding a method to service client to get current operation context
from that , something like
Servi
