<html><body bgcolor="#FFFFFF"><div>My take is to use what Rick has done. It's out there, no point in redoing it. The other idea if you want something from Red Hat would be to talk to the SnowDrop guys and have them do a Spring / CDI module (in keeping with the idea of the main project hosting the integration, not Seam). <br><br>Sent from my iPhone</div><div><br>On Jun 29, 2011, at 7:28, Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>Hi Team,<br><br>3 weeks ago I started a consulting mission in a big Insurance company that is Redhat / JBoss customer. They use most of Java EE 5 implementation provided by JBoss 5 EAP except for EJB 3. No EJB because it's also a Spring Shop. One of my missions is to help them to build their next official stack based on JBoss EAP 6 (which should be out in January). So I try to promote full Java EE 6 stack (with CDI and EJB 3.1) and put Spring aside as an alternative/Legacy framework. But it won't work if they don't have a supported solution to use their old Spring components / Knowledge in this new stack.<br>
More globally one big objection I encounter very often with the adoption of CDI (at least in France) is investment done in Spring. So if we want to facilitate the adoption we have to provide a Bridge with Spring to allow devs to integrate the "de facto standard" in the "official standard".<br>
I know that Rick Hightower and CDISource Team wrote a nice extension on the subject (<a href="https://github.com/CDISource/cdisource"><a href="https://github.com/CDISource/cdisource">https://github.com/CDISource/cdisource</a></a>) but I think such a module should be endorsed by a company that'll provide support on it like RH.<br>
Seam 2 provided this Bridge so it seems normal to provide it as well in Seam 3.<br>What is your opinion ?<br><br>Thanks,<br clear="all"><br>-- <br>Antoine Sabot-Durand<br><br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>seam-dev mailing list</span><br><span><a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a></span><br></div></blockquote></body></html>