cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Smyth (JIRA)" <>
Subject [jira] Assigned: (CXF-674) Make Spring XML extensions consistent
Date Fri, 01 Jun 2007 23:11:17 GMT


Andrea Smyth reassigned CXF-674:

    Assignee: Andrea Smyth

> Make Spring XML extensions consistent
> -------------------------------------
>                 Key: CXF-674
>                 URL:
>             Project: CXF
>          Issue Type: Task
>          Components: Configuration
>            Reporter: Andrea Smyth
>            Assignee: 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
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:
> {}endpoint
> {}client
> {}server
> {}conduit
> {}destination
> {}conduit
> {}destination
> Elements that may appear as top level beans (and referrred to elsewhere):
> {}enableColoc (currently has no schema)
> {}object (currently has no schema)
> {}soap
> {}failover (currently has no schema)
> {}trustDecider
> {}basicAuthSupplier
> {}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.

View raw message