While I think that a spring class to read the avalon descriptor is cool I also think it has a couple of drawbacks to take into consideration:
1) the avalon descriptor is in the phoenix function: in the current ant build you cannot make a function to depend on another functions. Maybe Robert has a solution for this. 2) Spring beans configuration is much more powerful than avalon assembly descriptor, so reading the descriptor will give us big compatibility and simplicity in moving to spring, but won't let us to use the more expressive spring configurability. Just my 2 cents, of course you should keep working on your idea. Stefano Bernd Fondermann ha scritto: > Hi, > > For the next weeks, I plan to improve the Spring integration branch. > The aim is to make it fit for trunk, as an experimental deployment module. > > Currently, the stuff at > http://svn.apache.org/repos/asf/james/server/sandbox/spring-integration > contains two different code bases, > src/main/ = my work, working with 2.3.0 > src/trunk/ = Joachim's work, working with trunk at that time > This has to be sorted. > > ATM, we have to translate james-assembly.xml into Spring beans > definition. I want to reuse james-assembly.xml in Spring by writing a > "mapper bean factory". Switching between deployments would be rather > easy then. > > WDYT? > > Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
