cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Mazza (JIRA)" <>
Subject [jira] [Commented] (CXF-4719) Annotation for web service endpoint
Date Wed, 02 Jan 2013 22:36:12 GMT


Glen Mazza commented on CXF-4719:

Hi Jason.  No, the requirement was not *just* to eliminate the XML, because Freeman already
provided a solution to Torben that would do that (namely, CXFNonSpringServlet), but Torben
in his response (which I requoted) clearly indicated that such a non-Spring solution would
be an unwanted "complex alternative".  Also, his comment in the Wiki:
further indicates he wants Spring annotations.

I haven't researched Spring 3.1 annotations, but from what I understand from Torben, it apparently
provides a generic way to convert *any* Spring XML beans file to annotations, including our
own cxf-servlet.xml file.  *That* is what will make him happy.  If Spring can indeed do this
in a generic fashion we may have nothing to do on our side to support it other than upgrade
to Spring 3.1 or more recent, which if I understand from Dan is planned in CXF 2.8.

What you're proposing may still be of value with CXFNonSpringServlet (although it doesn't
use XML files anyway--primarily Java API and annotations IIUC:,
or if I'm overestimating Spring 3.1 annotation capabilities. I'm just leery of putting something
in if its going to be redundant anyway once we upgrade to Spring 3.1.  Once you put functionality
in, it is frequently difficult to remove later due to backwards compatibility concerns.  That
was my main concern.

> Annotation for web service endpoint
> -----------------------------------
>                 Key: CXF-4719
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Torben Vesterager
> CXF is the only thing I'm using that still needs a spring configuration XML.
> All other components are configurable via annotations.

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

View raw message