cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-5362) Spring jaxrs scheme and bean definition parser must allow alternative property setting
Date Fri, 25 Oct 2013 14:20:31 GMT

    [ https://issues.apache.org/jira/browse/CXF-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805326#comment-13805326
] 

Daniel Kulp commented on CXF-5362:
----------------------------------

serviceBeans is mapped in the schema to xsd:anyType so pretty much anything can go in the
serviceBeans from a schema perspective.  Thus, I'm not really sure what you need to do that
cannot already be done.

That said, if we had to extend this, I'd prefer a simple "ref" attribute on the serviceBeans
that would allow it to refer to some other spring bean (that would have to evaluate to a collection
or a single bean):

{code:xml}
<bean name="foo">
    <list> ......</list>
</bean>

<jaxrs:server>
	<jaxrs:serviceBeans ref="foo"/>
</jaxrs:server>
{code}

> 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
>
> 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#6144)

Mime
View raw message