Re: [Springframework-developer] Bean order in applicationContext.xml changed? How to force order.

[Colin S. <col...@ex...>]

Hi Jon,

You can also use the 'depends-on' attribute on each bean, to 'manually' 
force dependencies, in addition to the dependencies expressed by 
bean-refs as properties.

Regards,
Colin

Jon Mountjoy wrote:

>Hi,
>
>I used to use M2, now M4.
>
>I suspect that something has changed between the two versions, with
>respect to the order in which beans that are declared in
>applicationContext.xml, are instantiated.  Unfortunately I can't
>immediately check this as rolling back my changes are going to take a
>few hours.  Can anybody confirm that this has taken place?  Previously,
>I believe the syntactic order played a role (subject to dependency
>resolution).
>
>I have a nasty situation in which as my controllers are loaded, they
>register security  information about themselves with a class.  A
>"master" controller that needs to be loaded last, uses this registered
>information in its configuration.  In M2 I placed this class last in
>the dispatcher-servlet.xml, and it got instantiated last.  
>
>Is there anyway that I can specify this dependency, or change some
>Spring component to honour syntactic order as much as possible?
>
>Thanks
>Jon
>
>  
>