hi hampus, great to hear that it works!
as mentioned before, you should definitely consider to use the controlled bootstrapping add-on, because the bootstrapping order in jee 5 app-servers isn't always deterministic. (there is also a maven repo which contains the deployed artifacts.) regards, gerhard http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/8/18 Hampus Wingren <[email protected]> > Hi again, > > My bad, I had Junit tests deployed with my application and the annotation > scanner picked up @RunWith and so forth without finding them (because I > don´t deploy the JUnit jar). > No it seems to be working ;-) > > Thanks for all your help! > > Regards, > Hampus > > -----Original Message----- > From: Gerhard Petracek [mailto:[email protected]] > Sent: den 18 augusti 2011 22:46 > To: MyFaces Discussion > Cc: Udo Schnurpfeil > Subject: Re: Window ID prototype, MyFaces extension > > hi hampus, > > maybe udo had this (owb) exception as well and can help you with that. > (otherwise we have to look at the details.) > > fyi: if there are further questions about owb itself, you are also very > welcome to send them to the mailing list of owb [1]. > e.g. mark and i and for sure the owb community in general will be happy to > answer your questions about owb. > > the second exception is caused by the first one. > however, if you solve the first one and you still get the second one, you > need [2]. > this add-on is required for some jee 5 servers to ensure the correct > bootstrapping order. > > regards, > gerhard > > [1] http://openwebbeans.apache.org/owb/mail-lists.html > [2] > > http://code.google.com/a/apache-extras.org/p/myfaces-codi-addons/source/brow > se/#hg%2Fcontrolled_bootstrapping_owb > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces > > > 2011/8/18 Hampus Wingren <[email protected]> > > > Ok, so I´ve tried with open webbeans and codi on websphere 6.1 but I > > keep ending up with: > > > > Caused by: > > org.apache.webbeans.corespi.scanner.AnnotationDB$CrossReferenceException > > at > > > > org.apache.webbeans.corespi.scanner.AnnotationDB.crossReferenceMetaAnnotatio > ns(AnnotationDB.java:173) > > at > > > > org.apache.webbeans.corespi.scanner.AbstractMetaDataDiscovery.crossReference > Beans(AbstractMetaDataDiscovery.java:229) > > ... 91 more > > > > And later on during startup: (I guess this error could be caused by > > the first one) > > > > Caused by: java.lang.IllegalStateException: no > > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvide > > r in place! Please ensure that you configured the CDI implementation > > of your choice properly. If your setup is correct, please clear all > > caches and compiled artifacts. If there is still a problem, try one of > > the controlled bootstrapping add-ons for the CDI implementation you are > using. > > at > > > > org.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider.getI > nstance(BeanManagerProvider.java:79) > > at > > > > org.apache.myfaces.extensions.cdi.core.impl.util.CodiUtils.getContextualRefe > renceByClass(CodiUtils.java:124) > > at > > > > org.apache.myfaces.extensions.cdi.jsf.impl.listener.phase.PhaseListenerExten > sion.consumePhaseListeners(PhaseListenerExtension.java:111) > > at > > > > org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleFact > oryWrapper.getLifecycle(CodiLifecycleFactoryWrapper.java:67) > > at javax.faces.webapp.FacesServlet.init(FacesServlet.java:119) > > > > I can´t really figure out what I´m doing wrong, are there some > > configuration options I must consider? > > > > Regards, > > Hampus > > > > > > -----Original Message----- > > From: Hampus Wingren [mailto:[email protected]] > > Sent: den 18 augusti 2011 13:52 > > To: MyFaces Discussion > > Subject: Re: Window ID prototype, MyFaces extension > > > > Ok, > > > > thanks a lot, I´ll give it a try! > > > > regards, > > Hampus > > > > On Thu, 18 Aug 2011 13:35:31 +0200, Gerhard Petracek < > > [email protected]> wrote: > > > hi hampus, > > > > > > we plan to release both codi v1.0.1 as well as owb v1.1.1 within the > > > next days. > > > udo (the reporter of the jira issues [1], [2]) already uses the > > > latest snapshots in a java 1.5 environment. > > > you can use those snapshots for the next days. you will see both > > > releases earlier than a first window-id-prototype in myfaces-core > > > (there is no fixed schedule for it - i'll continue with it after > > > releasing codi v1.0.1). > > > > > > regards, > > > gerhard > > > > > > [1] https://issues.apache.org/jira/browse/EXTCDI-198 > > > [2] https://issues.apache.org/jira/browse/OWB-582 > > > > > > http://www.irian.at > > > > > > Your JSF powerhouse - > > > JSF Consulting, Development and > > > Courses in English and German > > > > > > Professional Support for Apache MyFaces > > > > > > > > > > > > 2011/8/18 Hampus Wingren <[email protected]> > > > > > >> hi gerhard, > > >> > > >> That seems like a small price to pay. Do you have a timeframe for > > >> prototyping? > > >> > > >> I saw that´s it not a high prioritized item on the JSF 2.2 issue > > >> list, do we know if it will be included? > > >> I looked at apache owb but it seems to require java 6. Any other > > >> good cdi implementation other than weld? Looking at the issue lists > > >> for codi, it seems like weld is a major contributor to the issues. > > >> > > >> regards, > > >> Hampus > > >> > > >> I looked at apache owb but it seems to be requiring java 6 > > >> > > >> On Thu, 18 Aug 2011 13:07:41 +0200, Gerhard Petracek > > >> <[email protected]> wrote: > > >> > hi hampus, > > >> > > > >> > it might be available as a part of the myfaces specific api until > > >> > it gets accepted. however, it needs to be discussed on the dev > > >> > list as soon as we have a first prototype. > > >> > as soon as you upgrade to jsf 2.2 you will have to refactor some > > >> > parts, > > >> if > > >> > you are using the api manually. > > >> > > > >> > fyi: codi isn't bound to jee6. all you need is the cdi > > >> > implementation of your choice (in case of codi v1.0.1+ and owb > > >> > 1.1.1+ you can even use java > > >> > 1.5) > > >> > > > >> > regards, > > >> > gerhard > > >> > > > >> > http://www.irian.at > > >> > > > >> > Your JSF powerhouse - > > >> > JSF Consulting, Development and > > >> > Courses in English and German > > >> > > > >> > Professional Support for Apache MyFaces > > >> > > > >> > > > >> > > > >> > 2011/8/18 Hampus Wingren <[email protected]> > > >> > > > >> >> > > >> >> > > >> >> Hi, > > >> >> I´ve seen that you´re doing some prototyping for window > > >> >> sessions/ids for the JSF 2.2 spec. Is there any chance that you > > >> >> would make that available as an extension to the MyFaces Core > > >> >> dist for JSF 2.x? I think that it´s a killer feature but we > > >> >> don´t have the luxury to move to JEE 6 for the CODI stuff. > > >> >> Best regards, > > >> >> Hampus > > >> > > >> > > > > > >
