Personally, and I think a reasonable amount of users are in this situation,
and despite the fact that I would love to move to 1.2, I cannot.
We are using myfaces and facelets on a non-J2EE5 container, which means no
myfaces 1.2 for us, even if using facelets - although it would be possible
if we
Hi Adam,
In the Trinidad JSF 1.2 Support wiki
(http://wiki.apache.org/myfaces/Trinidad_JSF12_Support) you mentioned
that my current thinking is that this should happen when MyFaces
http://wiki.apache.org/myfaces/MyFaces switches their trunk to JSF
1.2. We should continue to keep around a JSF
Nope. FWIW, I'd personally be thrilled for the trunk to be 1.2 -
I've just assumed that this is not what the majority of our users
want, and would like to get some of the really big features -
like improved PPR - done before we move trunk to 1.2, so they're
available to all.
I think the
We're using 1.2. We didn't have any problems with the upgrade.
On 8/15/07, Adam Winer [EMAIL PROTECTED] wrote:
Nope. FWIW, I'd personally be thrilled for the trunk to be 1.2 -
I've just assumed that this is not what the majority of our users
want, and would like to get some of the really big
4 matches
Mail list logo