Mule

Component element error handling for instance-ref

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major 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-2178 Missing validation - either class or factory-ref/instance-ref must be provided for mule:component
    MULE-2694 NullPointerException in PojoServiceDefinitionParser when singleton-object element is used with instance-ref attribute
    MULE-5388 When 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 is
    MULE-4585 Exception handling - file routing
    MULE-2719 Implement top-level (reusable) components
    MULE-2316 Improved transformer-ref Handling
    MULE-4343 Support <spring:ref> tags in MuleHierarchicalBeanDefinitionParserDelegate
    MULE-5054 flow-ref element is not documented in schema
    MULE-2910 Replace 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)

Issue Links

Activity

Hide
andrew cooke added a comment - 21/Aug/07 10:58 AM

correction: scope="singleton" NOT singleton="true"

Show
andrew cooke added a comment - 21/Aug/07 10:58 AM correction: scope="singleton" NOT singleton="true"

People

Vote (0)
Watch (0)

Dates

  • Created:
    21/Aug/07 10:35 AM
    Updated:
    21/Aug/07 08:16 PM
    Resolved:
    21/Aug/07 08:16 PM