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
