Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 22 Jun 2011 15:18:49 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <764321648.29670.1308755929157.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CAMEL-4139) Unify blueprint and spring namespace
 parsing in camel-cxf
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Unify blueprint and spring namespace parsing in camel-cxf
---------------------------------------------------------

                 Key: CAMEL-4139
                 URL: https://issues.apache.org/jira/browse/CAMEL-4139
             Project: Camel
          Issue Type: Improvement
          Components: camel-cxf
            Reporter: Daniel Kulp
            Assignee: Daniel Kulp
             Fix For: 2.8.0


Currently, spring parses into a CxfEndpointBean whereas blueprint parses into a CxfEndpoint directly.   This mismatch then requires extra casting in the CxfComponent.   

Also, it means there are features supported by Spring that are not supported yet by blueprint  (like configuring interceptors).   I'm attaching a patch that removes the spring specific CxfEndpointBean stuff and allows both spring and blueprint to parse directly into the CxfEndpoint (well, subclasses of) so the two approaches can be maintained together.

It also reduces the usage of "Strings" for properties in CxfEndpoint and uses QNames where appropriate (added a Converter for that) and Class<?> for the service class.  That will allow OSGi to provide the Class directly instead of having to Class.forName the thing.  (still need to do that, but this is a start)


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira