cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5461) Add ws-securitypolicy-1.2.xsd to rt-ws-policy's schema resolution
Date Mon, 20 Jan 2014 16:16:24 GMT

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

Aki Yoshida resolved CXF-5461.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.9
                   2.6.12
                   3.0.0-milestone2

> Add ws-securitypolicy-1.2.xsd to rt-ws-policy's schema resolution
> -----------------------------------------------------------------
>
>                 Key: CXF-5461
>                 URL: https://issues.apache.org/jira/browse/CXF-5461
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 3.0.0-milestone2, 2.6.12, 2.7.9
>
>
> The other security related schemas that are used to configure a policy based security
scenario are available as local schema files in rt-ws-policy. However, the schema for namespace
"http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" is missing. This leads to the
namespace handler waiting error when the policy is configured inline in the blueprint configuration.
> [         Blueprint Extender: 2] BlueprintContainerImpl         INFO  Bundle test_wssecpolicy_in_bp
is waiting for namespace handlers [http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702]
> Since other policy related security schemas are exposed from rt-ws-policy, we could put
this schema in rt-ws-policy (and not in rt-ws-security).
> Note that one could avoid this problem by externalizing the policy part.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message