Trinidad+Mojarra
Friday Apr 04, 2008
Today I was asked if Trinidad required MyFaces to work as it's a MyFaces project.
There seems to be some misconception about component sets and JSF.
The key here is that component sets, assuming they code to the spec, can run
on *any* JSF compliant runtime. This means that Trinidad should run on either
MyFaces or Mojarra.
I've worked on and off with a couple of the Trinidad developers over the years
where I've received feedback regarding issues running Trinidad on Mojarra (which
we've always tried to address in a timely fashion). So I know by word of mouth
that it works, but today I decided to try it out for myself.
I downloaded the Trinidad 1.2.7 demo (for JSF 1.2) and deployed to GlassFish V2UR1.
After doing so I was able to run the Survey demo and browse through the component
guide without issue.
Some basic information about Trinidad:
- Partial-page rendering support for all Trinidad components (read Ajax)
- Client-side validation support
- Dialog framework
- pageFlowScope for inter-page communication
to color choosers, accordion panels, progress indicators, and many others you'd
expect to find in a robust component set. I'd recommend going through the
demo to view each of them in action.










