Noel J. Bergman wrote: Noel, your comments represent a mighty and worthy roadmap. There is a lot to chew on, here are a few initial comments.
<snipped/> > As for XBean, I favor OSGi interfaces, particularly as OSGi > and Sun are cooperating via the JCP to establish what will > become the official standard interfaces. ApacheDS and Derby > are already available as OSGi bundles, too. If it is correct > that XBean can serve as a convenience layer on top of OSGi, > that might be reasonable direction. I too would favour OSGi. As JSR 291, it has rocketed through the JSR stages and has been approved without change, though not without controversy, see http://www.theserverside.com/news/thread.tss?thread_id=39456. There may be merits in other solutions, but they are minor compared to a sound emerging standard. In the future, http://www.eclipse.org/proposals/ecp/ may be of interest. > > You could post a small piece as an example. I'd like to see > that example, and some discussion, as a prelude to discussion. > > The best place to start might be to refactor the existing > services into plain POJO services and then look at how we > want to tie those back into a particular container. Not sure that this is the best place to start. In an earlier post on this thread I suggested that we develop a compatibility layer between the semantics of the new container and the Avalon interfaces. Such a layer would give us working code from day one. Thereafter we could port code to run natively in the new container while always maintaining a working code base. After achieving this milestone, we could begin exploring the best ways to refactor our code base. <snipped/> Cheers -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
