On Thu, Feb 2, 2012 at 8:07 PM, Bruno Antunes <[email protected]> wrote: > no I'm serious, what's the joke for you? > I think Java EE is important for the actual java Apps. I think Spring and > everything else is cool, but java EE in gae would be awesome!
Wow. Ok. The problem is that GAE's transactional model is very badly mismatched to EJB's transactional model, even with XG transactions. You could, in theory, make it work - but it would be very, very rough. If you want a quick lesson, try turning off the "disable automatic transactions" property in datanucleus (<property name="datanucleus.NontransactionalRead" value="false"/><property name="datanucleus.NontransactionalWrite" value="false/>, I believe). I actually rather like working with EJB3 when working with RDBMSes, but I really couldn't imagine using them on GAE or any other kind of clustered database system. Jeff -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
