Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.0.0-M1
-
Fix Version/s: 2.0.0-M2
-
Component/s: Core: Configuration
-
Labels:None
-
User impact:Medium
-
Similar Issues:
MULE-3More flexible configuration mechanismMULE-3007Consider allowing other spring elements inside <mule>MULE-1394Refactor UMOEntryPoint for concurrency and more flexible implementationMULE-1241More flexible polling/scheduling support for receiversMULE-254Use XML namespaces for mule-spring-configurationMULE-936Consider basing the HTTP provider on AsyncWeb (http://asyncweb.safehaus.org/)MULE-2211Add Mule Element to SchemaMULE-5483Parsing Simple Component elements causes an NPE if they contain more than one attribute
MULE-5077 Root-bound attribute-based configuration for http endpoint doesn't workMULE-5185Should be possible to have more then one child element under a <when> element or the use of <processor-chain> should be forced
Description
The <mule> element is very restrictive - we could also have a more open approach via an alternative root element.
http://www.nabble.com/%3Cmule%3E-and-beans...--was-Re%3A--mule-scm---mule---8121--...--tf4357422.html