[ http://issues.apache.org/jira/browse/AXIS2-1735?page=all ]

Sanka Samaranayake resolved AXIS2-1735.
---------------------------------------

    Resolution: Fixed

Applied the uploaded patch.


> Policy Caching in the PolicyInclude in AxisDescription is incorrect
> -------------------------------------------------------------------
>
>                 Key: AXIS2-1735
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1735
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>         Environment: Linux version 2.6.17-gentoo ([EMAIL PROTECTED]) (gcc 
> version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, 
> pie-8.7.7.1)) #1 SMP PREEMPT Thu Jul 6 05:04:46 UTC 2006
> java version "1.5.0_08"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing)
>            Reporter: Sanka Samaranayake
>         Assigned To: Sanka Samaranayake
>         Attachments: PolicyInclude.java.patch
>
>
> PolicyInlcude.getPolicy() and PolicyInclude.getEffectivePolicy() use the 
> returns the computed Policy unless 
> 1) If a Policy is removed or updated in the current AxisDescription.
> 2) If the Policy or the effective Policy of the parent is changed.
> However the implementation doesn't seem to work properly and the caching is 
> removed in the submiited patch. We need to think carefully about how to 
> implement this and removal of erronous code seems to be the right thing for 
> the time being since Axis2 is still not heavily dependent of WS Policy

-- 
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]

Reply via email to