Hi guys
Do you have any clue on this case? Any help / idea might be helpful! As
Trinidad claims to be JSR-168 compliant, I expect the flaw to be in my
configuration files.. Has anyone got a working example of Trinidad running
in a portlet?
In the meantime I tried a few more things:
- Adding a
Lorin,
Trinidad should be JSR-301 compliant although to be frank, the Bridge is
brand spaking new so there might well be issues. What bridge are you
trying to run Trinidad with? If it's anything OTHER then the new
MyFaces portlet-bridge source, I really doubt it will work.
For this
Lorin
-Original Message-
From: Scott O'Bryan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 31, 2007 8:36 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Component renderer cannot be found in portal context
Lorin,
Trinidad should be JSR-301 compliant although to be frank, the Bridge
Cheers Lorin
-Original Message-
From: Scott O'Bryan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 31, 2007 8:36 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Component renderer cannot be found in portal context
Lorin,
Trinidad should be JSR-301 compliant although
, October 31, 2007 10:58 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Component renderer cannot be found in portal context
Naa. That's the old MyFaces bridge.
The current bridge is for JSF 1.2 only and is a myfaces subproject:
https://svn.apache.org/repos/asf/myfaces/portlet-bridge/trunk
with a download link for the bridge library?
Thanks again!
-Lorin
-Original Message-
From: Scott O'Bryan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 31, 2007 10:58 PM
To: MyFaces Discussion
Subject: Re: [Trinidad] Component renderer cannot be found in portal context
Naa. That's
6 matches
Mail list logo