[
https://issues.apache.org/jira/browse/CXF-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566726#action_12566726
]
Barry Fitzgerald commented on CXF-1425:
---------------------------------------
I had a think about this and thought that overriding the current list makes
most sense. I think that although a JAX-RS implementation needs to provide all
default providers there is no reason a given configuration needs them all. e.g.
one use case might never need JSON or XML just some custom provider of MIME
type "application/widget"
Secondly it gets awkward removing duplicates - how do you define a duplicate -
same type, same ProduceMime (what about overlaps?), same instance?
Ideally I think it would be great if you could in the spring config add
providers, remove providers and clear the whole list etc.
But I think this enhancement will most use cases and is a good start.
> Enhancement to JAX-RS spring configuration for registering providers
> --------------------------------------------------------------------
>
> Key: CXF-1425
> URL: https://issues.apache.org/jira/browse/CXF-1425
> Project: CXF
> Issue Type: Sub-task
> Components: REST
> Affects Versions: 2.1
> Reporter: Barry Fitzgerald
> Fix For: 2.1
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Enhancement to allow a list of custom providers be specified for a spring
> configured JAX-RS server. Syntax as below:
> <jaxrs:server id="bookservice"
> address="/">
> <jaxrs:serviceBeans>
> <ref bean="bookstore"/>
> </jaxrs:serviceBeans>
> <jaxrs:entityProviders>
> <bean
> class="org.apache.cxf.jaxrs.provider.JAXBElementProvider"/>
> <bean
> class="org.apache.cxf.jaxrs.provider.StringProvider"/>
> <bean
> class="org.apache.cxf.jaxrs.provider.BadgerFishProvider"/>
> </jaxrs:entityProviders>
> </jaxrs:server>
> <bean id="bookstore" scope="prototype"
> class="org.apache.cxf.systest.jaxrs.BookStore">
> </bean>
> This list will overwrite the default Entity Provider list and will be ordered
> as usual.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
