[
https://issues.apache.org/jira/browse/CXF-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aki Yoshida resolved CXF-5465.
------------------------------
Resolution: Fixed
Fix Version/s: 2.7.9
2.6.12
3.0.0-milestone2
> policy.xsd used in rt-ws-policy's blueprint configuration is inconsistent
> -------------------------------------------------------------------------
>
> Key: CXF-5465
> URL: https://issues.apache.org/jira/browse/CXF-5465
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.7.8
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Fix For: 3.0.0-milestone2, 2.6.12, 2.7.9
>
>
> According to the CXF documentation,
> http://cxf.apache.org/docs/schemas-and-namespaces.html
> the schema for CXF's policy configuration has namespace
> "http://cxf.apache.org/policy"; for both spring and blueprint, but the schema
> location is given as "http://cxf.apache.org/schemas/policy.xsd"; and
> "http://cxf.apache.org/schemas/blueprint/policy.xsd";, respectively.
> Although the lookup of these two schemas will unlikely occur at the same time
> (because one for only spring context and the other one for only blueprint
> context), assigning a namespace to two different locations with different
> contents could lead to an unexpected behavior. For example, schema at
> "http://cxf.apache.org/schemas/blueprint/policy.xsd"; has the target namespace
> set to http://cxf.apache.org/blueprint/policy.
> As it seems these two schemas can be unified into one schema without any
> dependency to spring or blueprint, we should use one unified schema for both
> contexts.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
