Hi Mark ! thanx again for the answer. I just tried to use Verborgs source because I couldn't use seamfaces and codi (which I would prefer of course) -> it's easier to look a 10 classes and 100 lines of code in a test project than at a full featured library.
Trying other CDI implementations with Glassfish like OpenWebBeans would be a very hard task if I believe some articles/even not impossible because Weld is included. Besides I'm not sure how many other problems I will produce and have to solve only to try out another solution. Of course I will try to give you further feedback but right now I'm running out of time in my project schedule so I have to make some tough decisions. My only last question for now is -> is there any detailed description/examle on how to deploy CODI in an enterprise project with an war and an ejb module (both cdi enabled) deployed in an ear. I'm still not sure if the problem isn't sitting right in front the keyboard :-) best regards Thomas ___________________________________ -----Ursprüngliche Nachricht----- Von: Mark Struberg [mailto:strub...@yahoo.de] Gesendet: Samstag, 27. November 2010 13:00 An: MyFaces Discussion Betreff: Re: AW: AW: AW: CODI 0.9.0 + Glassfish V3.0.1 + EAR Hi Thomas! First: You don't need Verborghs extension anymore. It it a good introduction sample to extension programming but was not production ready when I looked it the last time. I wrote an extension which uses the JSF-2 javax.faces.bean.ViewScope annotation to maintain a CDI Context implementation last year. The code is now included in CODI and Dan also used it as base for his Seam3 context. Our code also deals with proper cleanup, etc. For the glassfish issue: a) could you please test it with Apache OpenWebBeans (latest from trunk) and OpenEJB? David Jencks is currently working on a in depth geronimo integration of OWB. If you write a question to the d...@geronimo.apache.org list he might give you a quick info about the current status. b) you might also ping the weld-...@lists.jboss.org list to get more information about the glassfish status. And please keep on providing feedback, this is an important area in the industry and I bet there are still a few issues left open - so any help and especially feedback about common use cases is welcome! LieGrue, strub
