SpringAutowireConfigBuilder tests fail

Details

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

Description

This tests that Mule configuration in Spring Beans Xml works. The reason this does not work now is because in Mule 1.x the Mule Manager managed lifecycle ordering and initialisation of components. However, in Mule 2.0 the spring container does this by using the dependency information implicitly configured by the namespace handlers. In order for the AutowireConfigBuilder to work, users would need to go and manually configure the 'depends-on' attribute for most objects so they are initialised in order. So we may decide not to support a migration for the sort of configuration – does anyone have any ideas?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Perepelytsya added a comment -

Autowire and depends-on just exclude each other, I don't see any reason to waste time on it, if that is the case. Anyway, any autowiring is usable for all, but simple configs, so I'd call it the day and remove it from 2.0.0

Show
Andrew Perepelytsya added a comment - Autowire and depends-on just exclude each other, I don't see any reason to waste time on it, if that is the case. Anyway, any autowiring is usable for all, but simple configs, so I'd call it the day and remove it from 2.0.0
Hide
Permalink
Travis Carlson added a comment -

Removed the test based on Andrew's comment. r7164

Show
Travis Carlson added a comment - Removed the test based on Andrew's comment. r7164

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: