On Sun, Jun 13, 2010 at 4:15 AM, David Blevins <[email protected]> wrote:
> A much larger vision is that I'd really love to take EJB and break it up into > tiny little pieces. It's difficult to describe without writing a big > manifesto. I in fact have one that I started in July last year but never > finished an never published. I went ahead and published it anyway: > > http://blog.dblevins.com/2010/06/if-software-is-pizza-ejb-is-house.html > > I don't think it adequately expresses the conecept, but it's a start. I've read the blog entry and it was a thought-provoking reading which I loved. Following your metaphor(s), it was kind of having seen a pizza without having been able to taste it :) I'm too thought about something similar and was wondering what the starting point would be - there should be some kind of a DI container and the rest would be injected at appropriate places. Is XBean what fullfils the requirements? I'd love if OSGi was somehow involved that could mean OSGi+DI should be somehow merged and become THE starting place for the rest. Would you elaborate a bit more on the following: "All is fine until your bean throws a runtime exception and the container decides to rollback the current transaction on your behalf." Why is it an issue? Why would I not want to have it? What's the scenario? Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://jaceklaskowski.pl Kapituła Javarsovia 2010 - http://javarsovia.pl
