hi manuel, we just did a very basic test [1]. -> yes - it might be the case that the existing support module doesn't provide a workaround for it.
regards, gerhard [1] https://svn.apache.org/repos/asf/myfaces/extensions/cdi/trunk/examples/jsf-playground/hello_myfaces-codi_trinidad12/ http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2011/5/17 Manuel Hartl <[email protected]> > hi gerhard, > > > hi manuel, > > > > actually trinidad had to introduce special concepts and tricks to provide > > different features (esp. for jsf 1.x). > > it looks like at least one of them has problems with wrapped renderkits. > > (in codi we are just wrapping artefacts and intercepting calls to add > > functionality - but we don't change the behaviour of the wrapped > artefact.) > > > > i think the easiest way is to debug it. if you know the reason, we can > think > > about the next steps. > i did some tests and added one more wrapper method to your > trinidadrenderkitwrapper to use trinidad2. > this works for some page querys - but most result in a blank page. > > for comparison i tried using the same webapp with codi-jsf1 (with the > trinidad support module) and trinidad1. interestingly this resulted in > the SAME result :( > > so i assume the same problems exist in codi1/trinidad1 and codi2/trinidad2. > > it seems that the difference in working links / non working links is: > > - results in blank page: > > onclick="submitForm('globalForm',0,{source:'index_ssms:j_id_jsp_2090825442_2pc2:goInfo'});return > false;"> > > - works: > > onclick="TrPage._autoSubmit('globalForm','index_ssms:j_id_jsp_2090825442_2pc2:goAppManagement',event,0);return > false;" > > actually i dont know why these links are rendered differently (they are > generated in the same loop). maybe you have some additionly hint whats > the problem here. > > > regards, > manuel. > > > > > > > > regards, > > gerhard > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > > > > > 2011/5/17 Manuel Hartl <[email protected]> > > > >> hi gerhard, > >> > >>> by the way - welcome to the myfaces list! > >> thanks :) > >>> you can file a jira-ticket (new feature) in our jira [1]. > >>> > >>> you can try to find a workaround for a new support module or you come > up > >>> with a solution for improving trinidad to avoid such issues at all. > >> a good point. i asked myself if this is a problem of trinidad or codi. > >> so it is trinidad? > >> is there any information what the underlying problem is? do the trinidad > >> people know about this? > >> > >> regards, > >> manuel. > >> > >> > >> > >>> regards, > >>> gerhard > >>> > >>> [1] https://issues.apache.org/jira/browse/EXTCDI > >>> > >>> http://www.irian.at > >>> > >>> Your JSF powerhouse - > >>> JSF Consulting, Development and > >>> Courses in English and German > >>> > >>> Professional Support for Apache MyFaces > >>> > >>> > >>> > >>> 2011/5/17 Manuel Hartl <[email protected]> > >>> > >>>> Hi Gerhard, > >>>> > >>>> 1) to whom should i adress the feature request? > >>>> > >>>> 2) as the problem seems to be the same as with codi-jsf1/trinidad1, > the > >>>> solution should be not portable? > >>>> if i have some time this week i try to debug it. do you think it does > >>>> make sense to look at the trinidad12-module and try to > >>>> make it work for trinidad2 ? > >>>> > >>>> Regards, > >>>> Manuel. > >>>> > >>>>> hi manuel, > >>>>> > >>>>> if the trinidad-support module (myfaces-extcdi-trinidad12-support) > >>>> doesn't > >>>>> work any more with trinidad2 (it used to work), please file a feature > >>>>> request. > >>>>> it would be great, if you can also debug the issue and try to find a > >>>>> workaround which we can use in a myfaces-extcdi-trinidad20-support > >>>> module. > >>>>> regards, > >>>>> gerhard > >>>>> > >>>>> http://www.irian.at > >>>>> > >>>>> Your JSF powerhouse - > >>>>> JSF Consulting, Development and > >>>>> Courses in English and German > >>>>> > >>>>> Professional Support for Apache MyFaces > >>>>> > >>>>> > >>>>> > >>>>> 2011/5/17 Manuel Hartl <[email protected]> > >>>>> > >>>>>> Hi MyFaces-CODI-Team, > >>>>>> > >>>>>> i try to use the following in combination: > >>>>>> (JSF2 reference implementation) > >>>>>> Apache Myfaces CODI-JSF2 0.9.5 > >>>>>> Apache Myfaces Trinidad 2.0.0 > >>>>>> > >>>>>> 1) first i got the "No RenderingContext" exception, but this was > >> worked > >>>>>> around with > >>>>>> > >>>>>> /** > >>>>>> * Workaround for initializing the RenderingContext of Trinidad > >>>>>> * * @author Gerhard Petracek > >>>>>> */ > >>>>>> public class InitTrinidad { > >>>>>> protected void initTrinidad( > >>>>>> @Observes @BeforePhase(JsfPhaseId.ANY_PHASE) > >>>>>> PhaseEvent phaseEvent) { > >>>>>> if (RenderingContext.getCurrentInstance() == null) { > >>>>>> > >>>>>> > >>>>>> > >>>> > >> > tryToInstantiateClassForName("org.apache.myfaces.trinidadinternal.renderkit.core.CoreRenderingContext"); > >>>>>> } > >>>>>> } > >>>>>> } > >>>>>> > >>>>>> 2) now i am getting problems with RenderKit > >>>>>> > >>>>>> > >>>> > >> > org.apache.myfaces.extensions.cdi.jsf2.impl.scope.conversation.InterceptedRenderKit > >>>>>> not supporting > >>>>>> the "DialogRenderKitService" > >>>>>> > >>>>>> i think there was a CODI-JSF1.2-Trinidad1.2-compat module for JSF1.2 > >>>>>> (myfaces-extcdi-trinidad12-support-0.9.5.jar) and it seems that this > >> is > >>>>>> needed for CODI2 / Trinidad2, too. > >>>>>> > >>>>>> -> is there a plan to have this module for CODI-JSF2 also? > >>>>>> > >>>>>> Regards, > >>>>>> Manuel. > >>>>>> > >>>>>> -- > >>>>>> > >>>>>> Dipl. Inform. Manuel Hartl > >>>>>> Software Architect > >>>>>> > >>>>>> FlexSecure-Logo KobilGroup-Logo > >>>>>> > >>>>>> FlexSecure GmbH > >>>>>> Industriestr. 12 > >>>>>> D - 64297 Darmstadt > >>>>>> Tel: +49 (0) 6151 501 23-18 > >>>>>> Fax: +49 (0) 6151 501 23-19 > >>>>>> > >>>>>> E-Mail: [email protected] > >>>>>> Internet: www.flexsecure.de > >>>>>> > >>>>>> Geschäftsführer: > >>>>>> Erwin Stallenberger, Markus Ruppert > >>>>>> > >>>>>> Amtsgericht Darmstadt HRB 8036 > >>>>>> Umsatzsteuernummer: DE 214745269 > >>>>>> > >>>>>> > >>>>>> > >>>> > >>>> -- > >>>> Dipl. Inform. Manuel Hartl > >>>> Software Architect > >>>> > >>>> FlexSecure-Logo KobilGroup-Logo > >>>> > >>>> FlexSecure GmbH > >>>> Industriestr. 12 > >>>> D - 64297 Darmstadt > >>>> Tel: +49 (0) 6151 501 23-18 > >>>> Fax: +49 (0) 6151 501 23-19 > >>>> > >>>> E-Mail: [email protected] > >>>> Internet: www.flexsecure.de > >>>> > >>>> Geschäftsführer: > >>>> Erwin Stallenberger, Markus Ruppert > >>>> > >>>> Amtsgericht Darmstadt HRB 8036 > >>>> Umsatzsteuernummer: DE 214745269 > >>>> > >>>> > >> > >> > >> -- > >> Dipl. Inform. Manuel Hartl > >> Software Architect > >> > >> FlexSecure-Logo KobilGroup-Logo > >> > >> FlexSecure GmbH > >> Industriestr. 12 > >> D - 64297 Darmstadt > >> Tel: +49 (0) 6151 501 23-18 > >> Fax: +49 (0) 6151 501 23-19 > >> > >> E-Mail: [email protected] > >> Internet: www.flexsecure.de > >> > >> Geschäftsführer: > >> Erwin Stallenberger, Markus Ruppert > >> > >> Amtsgericht Darmstadt HRB 8036 > >> Umsatzsteuernummer: DE 214745269 > >> > >> > > > > > -- > Dipl. Inform. Manuel Hartl > FlexSecure GmbH > > Industriestr. 12 > 64297 Darmstadt > > Tel. +49 6151 50123 18 > > E-Mail: [email protected] > www.flexsecure.de >
