Antoine, I believe this was discussed a while back and the biggest problem in doing such a solution was the package naming clash between Seam 2 and 3 that would prevent them both being in the same deployment.
There were probably other issues too Ken Sent from my iPhone On Nov 25, 2011, at 8:26, Antoine Sabot-Durand <[email protected]> wrote: > Reading the SeamNext thread and all these remarks about Seam 2 to Seam 3 > migration I was wondering how difficult would it be to create a Seam 2 CDI > extension to provide the same kind of bridge we have with Spring ? > > This bridge would be one way : using Seam 2 bean in CDI (the other way is not > relevant). It would help people to go thru the migration process don't you > think ? > > The biggest difficulty would probably be the Seam 2 navigation and providing > some kind of extension to merge JSF2 and Seam 2 navigation seems a bit tricky. > > > > 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
