Just FYI, here is a tracker for all JSF 1.2 issues ([1]). Good thing would be making the maven-faces-plugin able to generate *standard* components; maybe I have some "extra" time this weekend on this.
-Matthias [1] http://tinyurl.com/qjd6y On 8/1/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Simon, side question; are you interested in helping on the jsf 1.2 task? I am not speaking about Trinidad, I am speaking about MyFaces. There is currently no development going on on this road. Last commits where in June from Dennis and me; that's it. -Matthias On 8/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hello, > > Was there any decision made concerning JSF 1.2 and Trinidad? The spec is > compatible, however generics were added to the API so some Trinidad > classes will requires some changes, the components mainly. What is the > master plan concerning it? Stay with 1.1 as long as possible? Switch to > 1.2 as soon as MyFaces is stable with the new spec? > > Personally I would like to switch to 1.2 as soon as there's a stable spec > implementation, especially since Trinidad is still in incubation (thus > don't have that many users) and 1.2 is the standard for JEE 5. At worst, > those wanting 1.1 can use the old ADF Faces. > > So far, the main compatibility issues I found are with > ExternalContext.getApplicationMap, ExternalContext.getRequestMap, > ExternalContext.getSessionMap and UIComponent.getAttributes. Trinidad uses > an <Object, Object> semantic for all of those. However, JSF 1.2 forces > <String, Object> for all of those. > > > Regards, > > Simon Lessard > Fujitsu Consulting > -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
-- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
