anonymous wrote : How can I contribute to this effort? No need, it is already fixed in CVS
anonymous wrote : From a design perspective, how do you see the relationship between Seam and EJB on the long term? EJB3 was a *huge* improvement, but I really see Seam's component model taking over on the EJB front. EJB provides the solid foundation of a single component model that is re-usable in all kinds of environments. Seam provides the integration of this component model into the different environments (web-based applications, AJAX applications, ESB applications, rich-client applications, etc). Things which are truly re-usable between these various environments should work their way back into the EJB spec. anonymous wrote : This issue I faced is a good example: If I can call a Seam component from a JMX Service, and if Seam manages the transaction for me, why should I even care about EJBs at all?? Why is Seam managing the txn? It should not be, it is only managing the persistence context. I don't see any reason for introducing full-featured declarative tx, security and state management at the level of Seam. (Though we may decide to provide integration of something like Acegi, if someone can ever properly explain to me its value.) Yes, I _could_ build this stuff into Seam, but then I would be essentially reimplementing EJB3, in a nonstandard way, so what would be the point? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3951474#3951474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3951474 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
