Hello! <snip/>
>I meant: if you want to achieve always the same result as by using > cocoon.getComponent() and you > need an access to WebApplicationContext directly then go with our own > version of WebAppContextUtils > that is aware of context switching. Anyway, using cocoon.getComponent() is > always a safe option. > > > My concerns only go > > towards the order of context-loading. And this point is still confusing > due to Joergs reply > > within this thread. He said, that appctx-loading-order is aplphabetical > - how could this be, if > > my RCL-output after mvn jetty:run shows up with an alphabetic unordered > list??? > > Not sure about this detail (can check if needed) but mind you asking why > you bother? Spring works > following way: first it reads all configurations files and only then it > tries to resolve all the > dependencies, etc. Given that, the read order doesn't matter because you > always get the same result. > Or am I wrong here? No, you are right! I always dive in deeper, if things look that simple ;) In this case they really are and all I have to worry about for now is carefully connection of blocks to reflect bean-dependencies. Really nice! Best greetings, Patrick -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
