Snowdrop guy(s) here :). I discussed this with Shane previously. By and large, there are two things that you can consider for this integration:
- blanket Spring/CDI integration - this can live inside of Seam or outside (e.g Snowdrop or something else); I started a Spring/Seam module a while ago, but never got to finalize it properly, and there is also the CDISource stuff. Right now, I need to find a way to combine them as I believe that the integration must go deeper than bootstrapping and resolution by name/type: e.g. events/observers, qualifier handling etc. - specific Seam integration - bridging Spring with Seam 3 specifically, and its various modules - e.g. transactions, persistence, qualifiers; My plan was to work on this (at least the Spring/CDI part) after AS7 is released - basically in July/August. I needed to focus on supporting Snowdrop proper on AS7 first :). ----- Original Message ----- > From: "Jason Porter" <[email protected]> > To: "Antoine Sabot-Durand" <[email protected]> > Cc: [email protected] > Sent: Wednesday, June 29, 2011 11:03:02 AM > Subject: Re: [seam-dev] Don't we need a Seam - Spring module ? > 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). > Sent from my iPhone > On Jun 29, 2011, at 7:28, Antoine Sabot-Durand < > [email protected] > wrote: > > Hi Team, > > > 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. > > > 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". > > > I know that Rick Hightower and CDISource Team wrote a nice > > extension > > on the subject ( https://github.com/CDISource/cdisource ) but I > > think such a module should be endorsed by a company that'll provide > > support on it like RH. > > > Seam 2 provided this Bridge so it seems normal to provide it as > > well > > in Seam 3. > > > What is your opinion ? > > > Thanks, > > > -- > > > Antoine Sabot-Durand > > > _______________________________________________ > > > seam-dev mailing list > > > [email protected] > > > https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/seam-dev
_______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
