On 2/1/07, David Woldrich <[EMAIL PROTECTED]> wrote:
Do I have your attention yet? :)
you have mine i'm not an expert but i'll try an initial response
I just installed ApacheDS, which is the new Apache LDAP java server, in about 50 seconds as a plugin INSIDE my Geronimo server using the deployer tool and a .car file I downloaded from http://geronimoplugins.com. The mind boggling implications of this new development are just too much for me to reckon properly right now. EJB, JMS, and now LDAP all in one JavaVM! I have literally been dreaming of this for years, and the ApacheDS install was so painless. I am seeing the future. But, I'll be the first to admit it, I am greedy and I want a lot more. I want mail and news servers in Geronimo too, and I want mailets that can call local EJB's that I can redeploy at will (or perhaps even make local EJB's that are themselves mailets.)
mailets that are EJB sounds better than calling EJBs from mailets but POJOs with context sound even better (cool to mix in with service buses etc) bit like activication specification message beans (mail is just another message, after all)
Hot redeployable mailets would be something nifty.
+1 some sort of mailet packaging would be very cool (but i was saving this subject for another day)
Practically everything I care about running with are apache projects, and maybe over time they start converging on and sharing dependencies within the Geronimo server. Total memory footprint goes down. Another big win for Apache. I understand there are architectural thingies in James to consider and phoenix and whatnot. I understand that there's a lot of time and investment in the existing architecture. And I'm not suggesting that James should not be able to run standalone, but I would like to be able to optionally deploy James to Geronimo as a plugin. Has someone in the know put any thoughts together on what it would take for this type of deployment of James? What showstoppers are there?
not sure there are really architectural issues with the container: the advantage of using an IoC container such as pheonix is that it's relatively easy to adapt to new envionments. but just running probably isn't enough. probably want to be able to integrate other services and this is where things become a little more difficult. ATM the database implementation uses torque. you'd probably want to hack a alternative implementation using JPA POJOs for the data binding. maybe could talk to OpenJPA over in the incubator. may need to think about threading and thread pooling
Perhaps we can organize a "James Bug Day" some Saturday similar to what the Parrot people are doing. Every month or so a bug day is organized where anyone who's interested in Parrot can get together on an IRC server and chat with the experts. I've personally taken todos off their list, knowing nothing ahead of time about Parrot, and worked on code and bugs with their help. Official committers on the project took my patches, reviewed them, and committed them for me. If there was ever an official James bug day, I would love to get involved, make some new friends, and (especially) do some work towards the James-As-Plugin end...
we'll review patches whether it's a bug day or not ;-) plan on being at the hackathon at apacheconEU? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
