cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (CXF-3975) Consolidate ws-rm configuration schema for spring and blueprint
Date Mon, 12 Dec 2011 22:53:31 GMT


Daniel Kulp resolved CXF-3975.

    Resolution: Fixed
> Consolidate ws-rm configuration schema for spring and blueprint
> ---------------------------------------------------------------
>                 Key: CXF-3975
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.5, 2.4.4
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>            Priority: Minor
>             Fix For: 2.4.5, 2.5.1
> Two almost identical configuration schemas (for spring and blueprint) are currently used
in the WS-RM component, as there are some XML attributes that are specific to one or the other
variant. The use of two schemas is associated with an increased cost in maintaining those
schemas as well as for WS-RM in particular, a significant overhead in providing a straightforward
configuration while reusing the jaxb based configuration classes for both variants.
> As defining the configuration schema for CXF's WS-RM component is on our hand and we
can define a single schema having the union of those attributes so that it can be used by
both types of configuration.
> The advantage of this unification is simplicity in the implementation code as well as
in the configuration. There is one schema and one namespace to maintain for both spring and
blueprint configurations.
> The drawback is a weakened syntax validation that could be avoided when two tailored
schemas are used for validation. However, there is typically always some gap between semantically
valid and only syntactically valid. And such divergence can be documented in the schema and
in the documentation to fill this gap. 
> Some additional information is at the dev@cxf archive

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message