You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2009/02/05 01:19:59 UTC
[jira] Created: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
-----------------------------------------------------------------------
Key: AXIS2-4233
URL: https://issues.apache.org/jira/browse/AXIS2-4233
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.4, 1.4.1, 1.5
Reporter: Alexis Midon
Here is the use case:
A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
A fix for axis2 1.5 will be really helpful.
[1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
[2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
[3] http://markmail.org/thread/ghsdxqdwnhec7puo
[4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
[5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Keith Godwin Chapman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671014#action_12671014 ]
Keith Godwin Chapman commented on AXIS2-4233:
---------------------------------------------
Alexis,
What is the URL you sent to request to?
Since Axis2 1.4 the way we calculate the effective policy changed a bit. Back then we didn't have the concept of storing the security policies in the binding hierarchy. Now to get the security policy correctly you have to dispatch to the correct binding. So essentially if a policy is attached st the binding level (Say the portName is SOAP12Binding) you need to send the request to serviceName.endpointName in order to pick that policy.
If a request is sent to serviceName alone we try to deduce the binding looking at the payload and in this case that may not work for you cause the payload is encrypted.
Could you try sending the request to serviceName.endpontName instead.
Thanks,
Keith.
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681628#action_12681628 ]
Nandana Mihindukulasooriya commented on AXIS2-4233:
---------------------------------------------------
Hi Alexis,
I think the behavior that was there in 1.3 is correct and if the service is dispatched we need to take that in to account when calculating the effective policy. To avoid security vulnerabilities, we will need to improve the PostDispatch verification handler of Rampart to check the policy after dispatch (both service and operation) and the policy that was used to verify security to see whether there are identical.
The work around you proposed works in this scenario but may cause problems in other scenarios. When RampartMessageData.KEY_RAMPART_POLICY is set, Rampart only takes that policy in to account so policies set in other levels of the heirachy will be ignored.
thanks,
Nandana
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671017#action_12671017 ]
Alexis Midon commented on AXIS2-4233:
-------------------------------------
I sent the request to a "custom" URL, I have my custom dispatcher set up before the security phase. This dispatcher resolves the service. From the service, we should be able to fetch the right policy.
I'm not clear on what this BindingMessage is. Maybe I'm missing something here. So let me explain how I set up my policy. If I do something wrong, hit me.
So basically, I do it ala axis2 1.3.
I have a AxisService instance, a service.xml document containing the policy only. With a ServiceBuilder, I "populate" the service. [1]
This works perfectly fine in axis2 1.3, as I said in my previous comment, the MessageContect will fetch the policy from the service instance.
Aren't we suppose to have the same behavior in 1.4? May you lead me through the migration steps? thanks.
[1] http://jukka.zitting.name/git/?p=ode.git;a=blob;f=axis2/src/main/java/org/apache/ode/axis2/hooks/main/java/org/apache/ode/axis2/hooks/ODEAxisService.java;h=1afded2e62ad68f6163f8cf87909017a5fbf3acb;hb=refs/heads/APACHE_ODE_1.X#l100
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-4233.
--------------------------------------
Resolution: Fixed
Seems like issue is fixed
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672436#action_12672436 ]
Alexis Midon commented on AXIS2-4233:
-------------------------------------
A workaround is to the busywork for Axis2. A custom dispatcher resolves the policy in a way similar to what axis2 1.3 used to do:
Policy policy = PolicyUtil.getMergedPolicy(new ArrayList(service.getPolicySubject().getAttachedPolicyComponents()), service);
messageContext.setProperty(RampartMessageData.KEY_RAMPART_POLICY, policy);
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated AXIS2-4233:
--------------------------------
Priority: Blocker (was: Major)
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4233) Regression in
MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681651#action_12681651 ]
Amila Chinthaka Suriarachchi commented on AXIS2-4233:
-----------------------------------------------------
Can you please have a look at with a build from trunk.
I changed the getEffectivePolicy method to look in to service as well.
thanks,
Amila.
> Regression in MessageContext#getEffectivePolicy between 1.3 and 1.4/1.5
> -----------------------------------------------------------------------
>
> Key: AXIS2-4233
> URL: https://issues.apache.org/jira/browse/AXIS2-4233
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5, 1.4.1, 1.4
> Reporter: Alexis Midon
> Priority: Blocker
>
> Here is the use case:
> A security policy is attached to my service (using a service.xml document and a ServiceBuilder).
> A message comes in, and reaches the RampartReceiver. At this point *only* the targeted service has been resolved by the preceding dispatchers, so no operation nor AxisMessage [4] are attached to the MessageContext yet . Actually the information required to resolve the operation is encrypted. So the MessageContext knows about the service *only*.
> Then the RampartReceiver tries to get the policy to be applied. This is done in RampartMessageData. To do that, MessageContext#getEffectivePolicy is invoked.
> In axis2 1.3, MessageContext#getEffectivePolicy [1] has a logic to retrieve the policy from the service instance. But in axis2 1.4 [2], the logic is different and never tries to get the policy from the service. So Rampart cannot do its job, and my service invocation fails :(
> To get the effective policy, the current implementation of MessageContext#getEffectivePolicy uses an instance of AxisBindingMessage if any. But AxisBindingMessage also requires the operation to be known [5] So I cannot workaround my problem, afaik.
> It seems that this issue has already been spotted [3] but I haven't found any related Jiras. And the regression is still in 1.5.
> A fix for axis2 1.5 will be really helpful.
> [1] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.3/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [2] http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/context/MessageContext.java
> [3] http://markmail.org/thread/ghsdxqdwnhec7puo
> [4] line 114, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/engine/AbstractDispatcher.java
> [5] line 275, http://svn.apache.org/repos/asf/webservices/axis2/tags/java/v1.4.1/modules/kernel/src/org/apache/axis2/description/AxisBindingMessage.java
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.