On 6/6/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Created a ticket [1]

btw. there was version 2.0 already mentioned. Any kickoff for JSF 2.0 ideas yet?

Ideas are being gathered (you can submit your favorites via the same issue tracking system), but there hasn't been a formal roadmap for JSF.next schheduled yet.  Once it is, there will be a formal announcement of a JSR from the JCP, plus a "call for experts" to be on the expert group.  When that happens, it would be very much appropriate that Apache have a representative on the EG, and it would seem to make the most sense that this rep be someone from the MyFaces community.

In the interim before the formal announcement, talk to Ed Burns and Roger Kitain, who were the co-spec leads for 1.2 (and AFAIK that's not changing for future versions, but I'm not as intimately connected with the specs world in my Creator architect role -- instead, I'm a customer :-) about the kinds of areas you would like to see a 2.0 spec cover.

-Matthias

Craig

[1] https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=176

On 6/6/06, Craig McClanahan < [EMAIL PROTECTED]> wrote:
>
>
>
> On 6/6/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> > CONVERTER_ID =  "javax.faces.DoubleTime "
>
>
> Looks like a spec bug due to a cut-n-paste error in the RI's API classes.
> If so, the correct thing to do would be to report feedback via the website
> on the spec cover (
> https://javaserverfaces-spec-public.dev.java.net) so that
> it can get addressed as an errata, or included in a maintenance version of
> the 1.2 spec.
>
> Until then, though, I'd recommend you keep it ... this is the kind of
> mechanical detail that the API signature tests in the TCK will likely flag
> if it's missing.
>
> Craig
>
>
>
> > On 6/6/06, Matthias Wessendorf < [EMAIL PROTECTED]> wrote:
> > > Any reason for keeping [1] ?
> > >
> > > -Matthias
> > >
> > > [1] http://tinyurl.com/gjdxe
> > >
> > > On 6/5/06, Matthias Wessendorf < [EMAIL PROTECTED] > wrote:
> > > > Ah,
> > > >
> > > > thanks. Some are some issues also the reasons, why UIComponent is not
> > > > an interface?
> > > >
> > > > -Matthias
> > > >
> > > > On 6/5/06, Adam Winer <[EMAIL PROTECTED]> wrote:
> > > > > Backwards compatibility - at least of a sort;  you won't get
> > > > > AbstractMethodErrors when using 1.1-compiled subclasses.
> > > > >
> > > > > -- Adam
> > > > >
> > > > >
> > > > > On 6/5/06, Matthias Wessendorf < [EMAIL PROTECTED]> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > does anybody know why the methods added to ViewHandler or
> > > > > > ExternalContext in 1.2 are not abstract, like their *old* JSF 1.1
> > > > > > counterparts ?
> > > > > >
> > > > > > -Matthias
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > > Aechterhoek 18
> > > > > > 48282 Emsdetten
> > > > > > blog: http://jroller.com/page/mwessendorf
> > > > > > mail: mwessendorf-at-gmail-dot-com
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > > Aechterhoek 18
> > > > 48282 Emsdetten
> > > > blog: http://jroller.com/page/mwessendorf
> > > > mail: mwessendorf-at-gmail-dot-com
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > Aechterhoek 18
> > > 48282 Emsdetten
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > Aechterhoek 18
> > 48282 Emsdetten
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>


--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Reply via email to