Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <4109046.1181769686499.JavaMail.jira@brutus>
Date: Wed, 13 Jun 2007 14:21:26 -0700 (PDT)
From: "Andrea Smyth (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Resolved: (CXF-674) Make Spring XML extensions consistent
In-Reply-To: <18049770.1179925936332.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrea Smyth resolved CXF-674.
------------------------------

    Resolution: Fixed

> 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
>            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 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.