Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
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-2178Missing validation - either class or factory-ref/instance-ref must be provided for mule:componentMULE-2694NullPointerException in PojoServiceDefinitionParser when singleton-object element is used with instance-ref attributeMULE-5388When SimpleServices inherits a component (element) same component instance is used and this introduces lifecycle problems
MULE-5917 Component class is not a required attribute in mule schema while it isMULE-4585Exception handling - file routing
MULE-2719 Implement top-level (reusable) componentsMULE-2316Improved transformer-ref Handling
MULE-4343 Support <spring:ref> tags in MuleHierarchicalBeanDefinitionParserDelegateMULE-5054flow-ref element is not documented in schemaMULE-2910Replace use of <singleton-object instance-ref="">
Description
If I use the config
{xml}<mule:component instance-ref="bean"/>{xml}I get an ugly error saying that there is no setter for "instance". This error goes away if I use singleton="true".
The problem seems to be one or more of:
- need better checking/error reporting of attributes
- singleton needs to be forced in this case?
- non-singleton use of instances is broken
(Assigning directly to you, Travis, hope that's OK)
correction: scope="singleton" NOT singleton="true"