You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2013/12/30 19:40:52 UTC
[jira] [Comment Edited] (CXF-5362) Spring jaxrs scheme and bean
definition parser must allow alternative property setting
[ https://issues.apache.org/jira/browse/CXF-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858979#comment-13858979 ]
Sergey Beryozkin edited comment on CXF-5362 at 12/30/13 6:39 PM:
-----------------------------------------------------------------
I've merged the code suggested by Dan; at the moment only jaxrs:serviceBeans and jaxrs:providers can take util:list, etc.
Dan, would you like me to update the code for setting in/out, inFault/outFault interceptors ? I will do it if you are OK with it,
Ivan: I think it is a good compromise, thanks for driving this enhancement
cheers, Sergey
was (Author: sergey_beryozkin):
I've merged the code suggested by Dan; at the moment only jaxrs:serviceBeans and jaxrs:providers can take util:list, etc.
Dan, would you like me to update the code for setting in/out, inFault/outFault interceptors ? I will do it if you are OK with it,
Ivan: I think it is a goof compromise, thanks for driving this enhancement
cheers, Sergey
> Spring jaxrs scheme and bean definition parser must allow alternative property setting
> --------------------------------------------------------------------------------------
>
> Key: CXF-5362
> URL: https://issues.apache.org/jira/browse/CXF-5362
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Reporter: Ivan Bondarenko
> Assignee: Sergey Beryozkin
> Fix For: 3.0.0-milestone2
>
>
> http://cxf.apache.org/schemas/jaxrs.xsd scheme in conjunction with JAXRSServerFactoryBeanDefinitionParser class must allow alternative property set.
> For example to set 'serviceBeans' now one must write:
> {code}<jaxrs:server>
> <jaxrs:serviceBeans>
> <ref bean="bean1"/>
> ...
> <ref bean="beanN"/>
> </jaxrs:serviceBeans>
> </jaxrs:server>{code}
> However there is no way to set this if number and set of beans is unknown beforehand (in case of different configurations etc).
> The easiest and most non-breaking way I see is to allow in scheme the default bean tags everywhere properties can be set. So user can do e.g. following:
> {code}<jaxrs:server>
> <property name="serviceBeans">
> _something_here_
> <property>
> </jaxrs:server>{code}
> Thus user can put almost anything (probably calculated in a complicated way) into 'serviceBeans' (and other properties).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)