Re: Trinidad on JDK 1.4
Scott, you are right, i was using com.liferay.util.jsf.apache.myfaces.context.MyFacesContextFactoryImpl. I tried to switch it to org.apache.myfaces.context.FacesContextFactoryImpl and it still worked but as soon as I switched to the Trinidad's FacesContextFactory i got the class cast exception. I guess I will need to do more investigation/learning and look at what you have plan to fix in Trinidad and try to help. As of ADFFaces 10.1.3.2. Any ideas when it will be released (even early access)? Is it going to support JDK 1.4. Thanks, Bruno On 10/11/06, Scott O'Bryan [EMAIL PROTECTED] wrote: Hmm interesting. The MyFaces Bridge portlet shouldn't work because of MYFACES-1383. My guess is you're also not registering Trinidad's FacesContextFactory which has some additional functionality (and will have more, ironically, as the Portal Project progresses). If you want to see my initial crack at the issues getting Trinidad to work, take a look at the Portlet component in Jira for Trinidad (ADFFaces). That's my initial crack at it based off some of the work I did for ADFFaces 10.1.3.2. I'm sure there will be more and I imagine there will be quite a few skinning tasks as well, but it's a start. And of course if you want to help fix any of this, have at it. I probably won't be able to get to the HARD CORE stuff for a couple weeks yet although I'm going to try to get the three needed foundation pieces in place to let people work on it before then. Scott Bruno Bernard wrote: Scott, Thanks for the reply and the details, this is precious information since I will need to make it work. We will not be using panelTabbed and inputFile As for the portal bridge, i am using my face. This is working for me (except that i get an exception in isIE maybe related to the bug that you are fixing). This is what i have Trinidad+jsf_facelet 1.1.6+myfaces 1.1.3+liferay 1.4.2 (with a fix i had to do) Bruno
Re: Trinidad on JDK 1.4
Unfortunately I don't know the release date. Should be available fairly soon I would imagine. I can try to check for you. I ALSO believe that it'll run in 1.4 and 1.5. I know the system is built in 1.4 anyway, but oracle QA's generally test it in 1.5. Don't get me wrong, I don't want to discourage you from using Trinidad. It is, essentially, the latest and greatest. It just doesn't yet have the portal stuff in it and is and will continue to become more JDK 1.5 centric. Scott Bruno Bernard wrote: Scott, you are right, i was using com.liferay.util.jsf.apache.myfaces.context.MyFacesContextFactoryImpl. I tried to switch it to org.apache.myfaces.context.FacesContextFactoryImpl and it still worked but as soon as I switched to the Trinidad's FacesContextFactory i got the class cast exception. I guess I will need to do more investigation/learning and look at what you have plan to fix in Trinidad and try to help. As of ADFFaces 10.1.3.2. Any ideas when it will be released (even early access)? Is it going to support JDK 1.4. Thanks, Bruno
Re: Trinidad on JDK 1.4
-1 to having to worry about what retroweaver does and does not support, and I certainly don't want to have to check in to two branches regularly. Thanks, Gabrielle Bruno Bernard wrote: Scott, Maybe Trinidad does not work completly with Portlets but it seems to have some support. It seems to work with me. I noticed 3 things so far: 1) org.apache.myfaces.trinidad.webapp.TrinidadFilter is not being called so the user agent is set to null. This cause an exception and I did a workaround to see how the rest was working. 2) Partial trigger does not work 3) the custom skins does not seems to be loaded (maybe related to 1) As of 1.4. I modified less than 10 lines of code and used retroweaver. It worked. To keep this working we would need to just make sure that we do not use 1.5 specific code that retroweaver does not support. Would you guys consider a branch that supports this + JSF 1.1. Maybe I am not the only one interested by this. Again myself and my company would consider to contribute. Bruno Scott O'Bryan wrote: Bruno, Actually, Trinidad does not yet work with portlets. :) That being said, most of the code base was ported over from ADFFaces which was originally written from 10.1.3. If 1.4 is a hard requirement, you might want to look at ADFFaces again. I believe the 10.1.3.1 release has enhancements to work with the portal system. Hopefully we'll get Trinidad up to speed very soon. -1 to reverting the renderkit to work with 1.4. It seems to me it's taking a step backward, especially as we (or Adam rather) ramp up to supporting JSF 1.2. Scott O'Bryan Bruno Bernard wrote: I am currently working for a company that had been using Oracle ADF for a while and we are currently planning to move to portlets. Since oracle ADF does not support portlets out of the box, we decided to look more closely into Trinidad which works with Portlets. One of our requirement is to use Java 1.4. After looking at this page (http://wiki.apache.org/myfaces/ADF_Faces/ToDo) I tried to see how much it was to run Trinidad on Java 1.4. It was easy and we've made it work. We are currently thinking to go for this solution and contribute to your project if you want.
Re: Trinidad on JDK 1.4
-1 - ditto to Gabrielle's comment. Gabrielle Crawford wrote: -1 to having to worry about what retroweaver does and does not support, and I certainly don't want to have to check in to two branches regularly. Thanks, Gabrielle Bruno Bernard wrote: Scott, Maybe Trinidad does not work completly with Portlets but it seems to have some support. It seems to work with me. I noticed 3 things so far: 1) org.apache.myfaces.trinidad.webapp.TrinidadFilter is not being called so the user agent is set to null. This cause an exception and I did a workaround to see how the rest was working. 2) Partial trigger does not work 3) the custom skins does not seems to be loaded (maybe related to 1) As of 1.4. I modified less than 10 lines of code and used retroweaver. It worked. To keep this working we would need to just make sure that we do not use 1.5 specific code that retroweaver does not support. Would you guys consider a branch that supports this + JSF 1.1. Maybe I am not the only one interested by this. Again myself and my company would consider to contribute. Bruno Scott O'Bryan wrote: Bruno, Actually, Trinidad does not yet work with portlets. :) That being said, most of the code base was ported over from ADFFaces which was originally written from 10.1.3. If 1.4 is a hard requirement, you might want to look at ADFFaces again. I believe the 10.1.3.1 release has enhancements to work with the portal system. Hopefully we'll get Trinidad up to speed very soon. -1 to reverting the renderkit to work with 1.4. It seems to me it's taking a step backward, especially as we (or Adam rather) ramp up to supporting JSF 1.2. Scott O'Bryan Bruno Bernard wrote: I am currently working for a company that had been using Oracle ADF for a while and we are currently planning to move to portlets. Since oracle ADF does not support portlets out of the box, we decided to look more closely into Trinidad which works with Portlets. One of our requirement is to use Java 1.4. After looking at this page (http://wiki.apache.org/myfaces/ADF_Faces/ToDo) I tried to see how much it was to run Trinidad on Java 1.4. It was easy and we've made it work. We are currently thinking to go for this solution and contribute to your project if you want.
Re: Trinidad on JDK 1.4
Scott, Thanks for the reply and the details, this is precious information since I will need to make it work. We will not be using panelTabbed and inputFile As for the portal bridge, i am using my face. This is working for me (except that i get an exception in isIE maybe related to the bug that you are fixing). This is what i have Trinidad+jsf_facelet 1.1.6+myfaces 1.1.3+liferay 1.4.2 (with a fix i had to do) Bruno Scott O'Bryan wrote: Bruno, We also have the following other issues: tr:inputFile will not work No PPR will work panelTabbed will not work if PPR doesn't work Image references will not work correctly etc. etc. etc. The list goes on an on. The problems you are discovering now are the same problems would would have trying to run ADFFaces before the portal enhancements were added. I don't doubt that Trinidad may run in a portal in a very limited (and inconsistant) capacity, but that does not constitute Portal support. Also, Trinidad will not work with the MyFaces bridge portlet at the moment until I check in a fix. Do you mind me asking what bridge portlet you are using? Scott Bruno Bernard wrote: Scott, Maybe Trinidad does not work completly with Portlets but it seems to have some support. It seems to work with me. I noticed 3 things so far: 1) org.apache.myfaces.trinidad.webapp.TrinidadFilter is not being called so the user agent is set to null. This cause an exception and I did a workaround to see how the rest was working. 2) Partial trigger does not work 3) the custom skins does not seems to be loaded (maybe related to 1) As of 1.4. I modified less than 10 lines of code and used retroweaver. It worked. To keep this working we would need to just make sure that we do not use 1.5 specific code that retroweaver does not support. Would you guys consider a branch that supports this + JSF 1.1. Maybe I am not the only one interested by this. Again myself and my company would consider to contribute. Bruno Scott O'Bryan wrote: Bruno, Actually, Trinidad does not yet work with portlets. :) That being said, most of the code base was ported over from ADFFaces which was originally written from 10.1.3. If 1.4 is a hard requirement, you might want to look at ADFFaces again. I believe the 10.1.3.1 release has enhancements to work with the portal system. Hopefully we'll get Trinidad up to speed very soon. -1 to reverting the renderkit to work with 1.4. It seems to me it's taking a step backward, especially as we (or Adam rather) ramp up to supporting JSF 1.2. Scott O'Bryan Bruno Bernard wrote: I am currently working for a company that had been using Oracle ADF for a while and we are currently planning to move to portlets. Since oracle ADF does not support portlets out of the box, we decided to look more closely into Trinidad which works with Portlets. One of our requirement is to use Java 1.4. After looking at this page (http://wiki.apache.org/myfaces/ADF_Faces/ToDo) I tried to see how much it was to run Trinidad on Java 1.4. It was easy and we've made it work. We are currently thinking to go for this solution and contribute to your project if you want.
Re: Trinidad on JDK 1.4
Scott, Maybe Trinidad does not work completly with Portlets but it seems to have some support. It seems to work with me. I noticed 3 things so far: 1) org.apache.myfaces.trinidad.webapp.TrinidadFilter is not being called so the user agent is set to null. This cause an exception and I did a workaround to see how the rest was working. 2) Partial trigger does not work 3) the custom skins does not seems to be loaded (maybe related to 1) As of 1.4. I modified less than 10 lines of code and used retroweaver. It worked. To keep this working we would need to just make sure that we do not use 1.5 specific code that retroweaver does not support. Would you guys consider a branch that supports this + JSF 1.1. Maybe I am not the only one interested by this. Again myself and my company would consider to contribute. Bruno Scott O'Bryan wrote: Bruno, Actually, Trinidad does not yet work with portlets. :) That being said, most of the code base was ported over from ADFFaces which was originally written from 10.1.3. If 1.4 is a hard requirement, you might want to look at ADFFaces again. I believe the 10.1.3.1 release has enhancements to work with the portal system. Hopefully we'll get Trinidad up to speed very soon. -1 to reverting the renderkit to work with 1.4. It seems to me it's taking a step backward, especially as we (or Adam rather) ramp up to supporting JSF 1.2. Scott O'Bryan Bruno Bernard wrote: I am currently working for a company that had been using Oracle ADF for a while and we are currently planning to move to portlets. Since oracle ADF does not support portlets out of the box, we decided to look more closely into Trinidad which works with Portlets. One of our requirement is to use Java 1.4. After looking at this page (http://wiki.apache.org/myfaces/ADF_Faces/ToDo) I tried to see how much it was to run Trinidad on Java 1.4. It was easy and we've made it work. We are currently thinking to go for this solution and contribute to your project if you want.
Re: Trinidad on JDK 1.4
Bruno, Actually, Trinidad does not yet work with portlets. :) That being said, most of the code base was ported over from ADFFaces which was originally written from 10.1.3. If 1.4 is a hard requirement, you might want to look at ADFFaces again. I believe the 10.1.3.1 release has enhancements to work with the portal system. Hopefully we'll get Trinidad up to speed very soon. -1 to reverting the renderkit to work with 1.4. It seems to me it's taking a step backward, especially as we (or Adam rather) ramp up to supporting JSF 1.2. Scott O'Bryan Bruno Bernard wrote: I am currently working for a company that had been using Oracle ADF for a while and we are currently planning to move to portlets. Since oracle ADF does not support portlets out of the box, we decided to look more closely into Trinidad which works with Portlets. One of our requirement is to use Java 1.4. After looking at this page (http://wiki.apache.org/myfaces/ADF_Faces/ToDo) I tried to see how much it was to run Trinidad on Java 1.4. It was easy and we've made it work. We are currently thinking to go for this solution and contribute to your project if you want.
