Consider allowing other spring elements inside <mule>

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: 2.0.0-RC2
  • Fix Version/s: None
  • Component/s: Core: Configuration
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

Before finalising schema for 2.0 it might be worth considerng allowing other spring elements in the root <mule> element to allow spring shortcuts to be used which are in other spring namespaces.

e.g.:
<context:property-placeholder/>

any many more...

Issue Links

blocks

Improvement - An improvement or enhancement to an existing feature or task. MULE-2731 Configuration shortcut for PropertyPlaceholderConfigurer

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Daniel Feist added a comment -

mmm. maybe this isn't an issue and it can go inside of a <beans> element?

Show
Daniel Feist added a comment - mmm. maybe this isn't an issue and it can go inside of a <beans> element?
Hide
Permalink
Daniel Feist added a comment -

If that's possible then it becomes:

<spring:bean id="propertyPlaceholderConfigurer"
      class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
    <spring:property name="location">
        <spring:value>email.properties</spring:value>
    </spring:property>
</spring:bean>

vs.

. . . extra namespace declaration ...... 

 <spring:beans>
    <context:property-placeholder location="email.properties"/>
 </spring:beans>
Show
Daniel Feist added a comment - If that's possible then it becomes: 
<spring:bean id="propertyPlaceholderConfigurer"
      class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
    <spring:property name="location">
        <spring:value>email.properties</spring:value>
    </spring:property>
</spring:bean>
vs. 
. . . extra namespace declaration ...... 

 <spring:beans>
    <context:property-placeholder location="email.properties"/>
 </spring:beans>
Hide
Permalink
Daniel Feist added a comment -

Can already do both scenarios.

Show
Daniel Feist added a comment - Can already do both scenarios.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: