Make Spring XML extensions consistent
-------------------------------------
Key: CXF-674
URL: https://issues.apache.org/jira/browse/CXF-674
Project: CXF
Issue Type: Task
Components: Configuration
Reporter: Andrea Smyth
All elements that can appear as children of the beans element should inherit
from beans:identified type and add attribute group cxf-beans:beanAttributes
defined in the http://cxf.apache.org/schemas/configuration/cxf-beans.xsd in
cxf-common-utilities. That group includes a name attribute that is handled in
the same was as Springs name attribute. i.e. its consituent parts (name is a
comma separated list of strings) are used as aliases. This is necessary in
order to identify beans by a strin gified QName (as these are not legal
xsd:IDs). Another attribute in this group is abstract and createdFromAPI. Code
in the cxf-common-utilities module can and should be used to parse these
attributes.
Affected elements that definitely can appear as top level beans are:
{http://cxf.apache.org/jaxws}endpoint
{http://cxf.apache.org/jaxws}client
{http://cxf.apache.org/jaxws}server
{http://cxf.apache.org/transports/http/configuration}conduit
{http://cxf.apache.org/transports/http/configuration}destination
{http://cxf.apache.org/transports/jms}conduit
{http://cxf.apache.org/transports/jms}destination
Elements that may appear as top level beans (and referrred to elsewhere):
{http://cxf.apache.org/binding/coloc}enableColoc (currently has no schema)
{http://cxf.apache.org/bindings/object}object (currently has no schema)
{http://cxf.apache.org/bindings/soap}soap
{http://cxf.apache.org/clustering}failover (currently has no schema)
{http://cxf.apache.org/transports/http/configuration}trustDecider
{http://cxf.apache.org/transports/http/configuration}basicAuthSupplier
{http://cxf.apache.org/ws/addressing}addressing
The purpose is to
a) reduce duplication in both Java and xsd code
b) bring consistency into the elements that users will most likely interact
with in their own configuration files: w.r.t. identification and abstractness
Spring XML extensions should behave just like plain Sring beans.
c) eventually allow use of Springs validating parser across all tests and demos.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
