What about discussing this point with CDIDource ? Their code could be a good base. I asked Rick if I could use it and he seemed to be very open on the subject... I could do it, except I need time to work on... a given JSR in which I'm supposed to be involved ;-).<br>
<br>Antoine<br><br><div class="gmail_quote">2011/6/29 Pete Muir <span dir="ltr"><<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It has been discussed multiple times, but it was never delivered on. I set it as a requirement for Seam 3.1 when I handed over to Shane, but not sure what has happened since.<br>
<div><div></div><div class="h5"><br>
On 29 Jun 2011, at 15:18, Antoine Sabot-Durand wrote:<br>
<br>
> Your smiley suggest that this has been already discussed / decided. I missed those discussion apparently. Sorry...<br>
><br>
> Antoine<br>
><br>
> 2011/6/29 Pete Muir <<a href="mailto:pmuir@redhat.com">pmuir@redhat.com</a>><br>
> Yes, we should do this :-)<br>
><br>
> Marius is the owner.<br>
><br>
> On 29 Jun 2011, at 14:28, Antoine Sabot-Durand wrote:<br>
><br>
> > 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" target="_blank">https://github.com/CDISource/cdisource</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>
> ><br>
> > --<br>
> > Antoine Sabot-Durand<br>
> ><br>
> > _______________________________________________<br>
> > seam-dev mailing list<br>
> > <a href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/seam-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Antoine Sabot-Durand<br>
> Manager technique<br>
> -------------------------------<br>
> Ippon Technologies<br>
> 3, rue Bellanger<br>
> 92300 Levallois Perret<br>
> t. 01.46.12.48.48<br>
> f. 01.46.12.48.49<br>
> p. 06.08.55.34.26<br>
> e. <a href="mailto:asd@ippon.fr">asd@ippon.fr</a><br>
> <a href="http://www.ippon.fr" target="_blank">www.ippon.fr</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Antoine Sabot-Durand<br>Manager technique<br>-------------------------------<br>Ippon Technologies <br>3, rue Bellanger<br>92300 Levallois Perret<br>t. 01.46.12.48.48<br>
f. 01.46.12.48.49<br>p. 06.08.55.34.26<br>e. <a href="mailto:asd@ippon.fr">asd@ippon.fr</a><br> <a href="http://www.ippon.fr">www.ippon.fr</a> <br>