On 6/5/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
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
Having been around James for a long time now, one of the things which I've seen cause us problems time and again is planning to make radical changes which can't be done incrementally. We simply don't have the resources. I agree with your general point, that this approach is probably not the "best" technical solution, but from a practical and "marketing" point of view it is very significant. 1/ We can "road test" James & Spring using James in a well understood state. 2/ We can offer James & Spring to "early adopters" who are looking for this integration 3/ It shows the world that we really are taking practical steps to recover from the implosion of Avalon and protect our users investment in James. 4/ We can evolve James to become less container specific without a flag day. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
