Well Trinidad is not an Oracle product, it's an Apache product.
Nonetheless, I imagine it would be a good bet that Oracle would want to
continue to support Trinidad going forward. That said, there is no
reason that someone couldn't start a new renderkit. The code is
open-sourced. I just don't think we can confine ourselves to "the next
big thing" without supporting existing frameworks. There are many
companies that have a vested interest in Tobago, Tomahawk, AND Trinidad
and would want to support these frameworks going forward.
To be fair, Trinidad has been in active development with tons of
developer resources being thrown at it for several years. Tomahawk and
Tobago for longer then that. This project will likely be a considerable
effort. My only concern is that maybe this effort is better spent
fixing the old renderkits and branching them into JSF 2.0 branches
rather then coming up with an new include-all renderkit.
If people were thinking seriously about this project, I would suggest
picking an existing renderkit as the foundation and going through it
piece by piece to support JSF 2.0 and streamline everything. Then I
would add the additional components and capabilities and call it good.
Scott
Mario Ivankovits wrote:
Hi!
Now it would be possible to update each component set to JSF 2.0...
but a Tomahawk/JSF2 is "expected" to be backward compatible. So it
would be difficult to radically change components or eliminate some
duplicates...
+1
I'd like to see this too, though, I think Oracle wouldn't give up
Trinidad. And Tobago also is (too?) different, no?
Ciao,
Mario
