[
https://issues.apache.org/jira/browse/CXF-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493168
]
Gary Tully commented on CXF-623:
--------------------------------
one further detail of the patch, the wildcard is a applied before any bean id
matching config such that a bean with an exact-name match can override any
wildcard.
> spring bean configuration should support simple wildcards
> ---------------------------------------------------------
>
> Key: CXF-623
> URL: https://issues.apache.org/jira/browse/CXF-623
> Project: CXF
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.0-RC
> Reporter: Gary Tully
> Attachments: patch-cxf-623.r534554.patch
>
>
> to apply configuration to a http destination I need to provide the following:
> <bean name="{http://www.test.com}MyPort.http-destination"; abstract="true">
> <property name="multiplexWithAddress" value="true"/>
> </bean>
> which matches a single port by name.
> I would like to be able to provide
> <bean name="*.http-destination" abstract="true">
> <property name="multiplexWithAddress" value="true"/>
> </bean>
> to indicate to apply the config to all http-destinations. To make this work
> in practice a class attribute is required, otherwise any wildcard would be
> matched against all beanNames. The package is probably not required in the
> className attribute.
> <bean name="*.http-destination" abstract="true" class="HttpDestination">
> <property name="multiplexWithAddress" value="true"/>
> </bean>
> To get Spring to merge wildcard and beanName specific config may be a
> chalenge but it would be great. Possibly it is a case of configuring once
> with the wildcard match and once with the specific name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
