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.
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
-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
-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
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
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
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
