Re: CODI No bean found for type

yes tomee v1.0 - before you contact the tomee community, please ensure that your setup is correct (e.g. CATALINA_HOME). regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2

Re: CODI No bean found for type

fixed in TomEE 1.0?? im using it and the problem still 2012/5/17 Gerhard Petracek > yes - they fixed the issue, added test-cases which should ensure the > compatibility and we deployed several demos successfully. > > regards, > gerhard > > http://www.irian.at > > Your JSF/JavaEE powerhouse - > J

Re: CODI No bean found for type

yes - they fixed the issue, added test-cases which should ensure the compatibility and we deployed several demos successfully. regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFac

Re: CODI No bean found for type

Gerhard, in my old post you told me this was a bug: [1] http://os890.blogspot.com/2012/01/codi-meets-tomee.html [2] https://cwiki.apache.org/confluence/display/EXTCDI/Intro#Intro-Servers http://old.nabble.com/CODI-%2B-TomEE-td33754910.html This is fixed in TomEE 1.0?? 2012/5/17 Gerhard Petr

Re: CODI No bean found for type

hi jose, it looks like myfaces-core gets started before owb in your case. regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2012/5/18 José Luis Cetina > Im chanching my

CODI No bean found for type

Im chanching my web app from glassfish to TomEE 1.0 (i want to use all the Apache Stuff). I have problem when i add CODI to my pom.xml Im getting this error: Caused by: java.lang.IllegalStateException: No bean found for type: org.apache.myfaces.extensions.cdi.jsf.api.config.JsfModuleConfig pom