[ 
https://issues.apache.org/jira/browse/CXF-4085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Freeman Fang resolved CXF-4085.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.6
                   2.5.3
                   2.4.7
                   2.3.10

commit fix
http://svn.apache.org/viewvc?rev=1240006&view=rev for trunk
http://svn.apache.org/viewvc?rev=1240008&view=rev for 2.5.x branch
http://svn.apache.org/viewvc?rev=1240011&view=rev for 2.4.x branch
http://svn.apache.org/viewvc?rev=1240014&view=rev for 2.3.x branch
                
> introduce 
> org.apache.cxf.jaxws.checkPublishEndpointPermissionWithSecurityManager for 
> EndpointImpl so that get chance to bypass SecurityManager Check in some cases
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4085
>                 URL: https://issues.apache.org/jira/browse/CXF-4085
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.3.10, 2.4.7, 2.5.3, 2.6
>
>
> currently we have a property 
> org.apache.cxf.jaxws.checkPublishEndpointPermission which can control use 
> AccessController or not(default behavior is not) when SecurityManager isn't 
> installed, I'd like to introduce another property like 
> org.apache.cxf.jaxws.checkPublishEndpointPermissionWithSecurityManager which 
> can control bypass SecurityManager or not, this could be useful when deploy 
> cxf endpoint in some container like websphere.
> If we explicitly specify this property as false, then get chance to bypass 
> the SecurityManager checking jaxws endpoint publish permission, by default if 
> we don't specify this property, it will always try to use SecurityManager to 
> check permission, keep same behavior as before.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to