You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Martin Marinschek <ma...@gmail.com> on 2006/09/26 20:57:53 UTC
[OFFTOPIC] What I wish that JSF 2.0 would be like...
Hi there,
Ed Burns, Jesse Alexander and me will be heading a discussion on what
our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
Munich, at the Oktoberfest.
So it's a good opportunity for both talking about JSF and drinking
beer - probably the best of the world. We'll meet up in:
http://www.weisses-brauhaus.de/
at 18:00
and if you're interested in coming, reply to this mail and I'll
include you in the reservation.
regards,
Martin
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Shinpei Ohtani <sh...@gmail.com>.
hi,
OGNL is a good to use :)
About EL, I hope it's evaluation mechanism should be separated from
application context,
so actual evaluation can be executed by JavaScript or Ruby.
It is more powerful and extensible, I think.
2006/9/27, Martin Marinschek <ma...@gmail.com>:
> Hmm, interesting. That could be handled in the ExpressionResolver, I guess.
>
> regards,
>
> Martin
>
> On 9/27/06, Angelo Luis <an...@gmail.com> wrote:
> > something i dream to JSF EL have is a null handle a la OGNL / webwork
> > pair....
> >
> > So if have a deep object graph like client.address.city.name in a input for
> > example the JSF dont throw a NullPointerException if i dont instanciate all
> > the object graph, just create him at runtime.
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
--
=============================
Shinpei Ohtani
shinpei.ohtani@gmail.com
=============================
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Matthias Wessendorf <ma...@apache.org>.
indeed, that sounds neat
On 9/27/06, Martin Marinschek <ma...@gmail.com> wrote:
> Hmm, interesting. That could be handled in the ExpressionResolver, I guess.
>
> regards,
>
> Martin
>
> On 9/27/06, Angelo Luis <an...@gmail.com> wrote:
> > something i dream to JSF EL have is a null handle a la OGNL / webwork
> > pair....
> >
> > So if have a deep object graph like client.address.city.name in a input for
> > example the JSF dont throw a NullPointerException if i dont instanciate all
> > the object graph, just create him at runtime.
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Martin Marinschek <ma...@gmail.com>.
Hmm, interesting. That could be handled in the ExpressionResolver, I guess.
regards,
Martin
On 9/27/06, Angelo Luis <an...@gmail.com> wrote:
> something i dream to JSF EL have is a null handle a la OGNL / webwork
> pair....
>
> So if have a deep object graph like client.address.city.name in a input for
> example the JSF dont throw a NullPointerException if i dont instanciate all
> the object graph, just create him at runtime.
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Angelo Luis <an...@gmail.com>.
something i dream to JSF EL have is a null handle a la OGNL / webwork
pair....
So if have a deep object graph like client.address.city.name in a input for
example the JSF dont throw a NullPointerException if i dont instanciate all
the object graph, just create him at runtime.
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Rogerio Pereira <ro...@gmail.com>.
Ah! Talk about JSF in the middle of this fest? I'm not sure. :)
Someday i'll meet with you guys!
2006/9/26, Martin Marinschek <ma...@gmail.com>:
>
> Hi there,
>
> Ed Burns, Jesse Alexander and me will be heading a discussion on what
> our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
> Munich, at the Oktoberfest.
>
> So it's a good opportunity for both talking about JSF and drinking
> beer - probably the best of the world. We'll meet up in:
>
> http://www.weisses-brauhaus.de/
>
> at 18:00
>
> and if you're interested in coming, reply to this mail and I'll
> include you in the reservation.
>
> regards,
>
> Martin
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
--
Yours truly (Atenciosamente),
Rogério (_rogerio_)
http://faces.eti.br
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Shinpei Ohtani <sh...@gmail.com>.
Hi all from Japan,
I love drinking beer, but obviously I can't go there.
So here is my thoughts that should be included JSF 2.0, just some ideas.
-No JSP please.Default view technology should be pure HTML.
(facelet is not good enough, I suppose.)
-Creating renderer are super painful to customize.
-No xml config. Annotation is better way to config.
However, for being much better, Convention over Configuration manner
is the way,
so no config is needed.
(See Ruby on Rails, and their philosophy.)
-Support Ajax application as default.
I hope some of the ideas are useful.
2006/9/27, Roger Keays <ro...@ninthavenue.com.au>:
>
> Hi Martin,
>
> Here are a couple of ideas I've jotted down:
>
> * Native support for conversation scope.
>
> * Support for partial requests (i.e. AJAX). I imagine this would be
> along the lines of standardising the request and response formats for
> partial requests, and requiring a javascript implementation.
>
> * Ability to invoke actions on first page request. When you're linked
> from other sites, or from a mail client you can't really expect them to
> send the whole state of the component tree, which would be needed to
> invoke an action from that tree (although this does work). Instead, you
> might be able to create a new action listener type which is invoked when
> the tree it is attached to is created/rendered. Of course, it'd have to
> fit into the lifecycle somehow. A simple use case for this would be a
> "click here to vote for struts" link in an email which should invoke a
> JSF Action{Listener}. Currently you'd probably do this with a
> PhaseListener or ServletFilter.
>
> * Ability to define converters for annotated classes (e.g. @Entity).
> We can do <converter-for-class>, which also works for interfaces, but
> there are cases where an annotation might indicate that a common
> converter could be used. In the case of @Entity, you might be able to
> use something like EntityManager.getId(entity).toString() to convert the
> class (somebody add getId() to JPA 1.1 please!).
>
> * Ability to use #{foo} as an lvalue. Maybe more specific to the EL
> spec, but ATM only #{foo.bar} can be used as an lvalue. Sometimes I just
> want to keep a simple string in the session scope and do things like
> <h:inputText value="#{foo}"/>, but instead I have to make a separate
> bean just containing a String.
>
> * Reinvestigate, as per Jabob's ideas, whether we /really/ need
> component state-saving. I got pretty confused when I wrote a simple
> regexp validator that kept forgetting what the regexp was. It was all
> there in the .xhtml file! That was until I learnt about state-saving
> (which was more than I really wanted to know).
>
> * Dump JSP, and make facelets standard.
>
> Happy Oktoberfest!
>
> Roger
>
>
> Martin Marinschek wrote:
> > Hi there,
> >
> > Ed Burns, Jesse Alexander and me will be heading a discussion on what
> > our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
> > Munich, at the Oktoberfest.
> >
> > So it's a good opportunity for both talking about JSF and drinking
> > beer - probably the best of the world. We'll meet up in:
> >
> > http://www.weisses-brauhaus.de/
> >
> > at 18:00
> >
> > and if you're interested in coming, reply to this mail and I'll
> > include you in the reservation.
> >
> > regards,
> >
> > Martin
> >
>
>
> --
> ----------------------------------------
> Ninth Avenue Software
> p: +61 7 3137 1351 (UTC +10)
> f: +61 7 3102 9141
> w: http://www.ninthavenue.com.au
> e: info@ninthavenue.com.au
> ----------------------------------------
>
>
--
=============================
Shinpei Ohtani
shinpei.ohtani@gmail.com
=============================
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Martin Marinschek <ma...@gmail.com>.
Cool. I'll take your input with me to the discussion. Thanks for all
the thoughts!
regards,
Martin
On 9/27/06, Shinpei Ohtani <sh...@gmail.com> wrote:
> Hi,
>
> > All I need is JSP definetely dropped, and a decent exception handling
> > mechanism! :D
>
> Yeah, I agree with you, tetsuo.
> We need good exception handling mechanism.
>
>
> 2006/9/27, tetsuo <ro...@gmail.com>:
> > All I need is JSP definetely dropped, and a decent exception handling
> > mechanism! :D
> >
> > Have fun, guys!
> >
> >
> > On 9/26/06, Roger Keays <ro...@ninthavenue.com.au> wrote:
> > >
> > > One more:
> > >
> > > * New listener for FacesServlet startup/shutdown. Some JSF
> > > extensions may need to do some initial configuration on startup and
> > > shutdown but these extensions can't add a ServletContextListener to
> > > web.xml. ATM you can get similar behaviour by using a PhaseListener and
> > > deregistering it after it is first run, but that is just a workaround
> > > really.
> > >
> > > Roger Keays wrote:
> > > >
> > > > Hi Martin,
> > > >
> > > > Here are a couple of ideas I've jotted down:
> > > >
> > > > * Native support for conversation scope.
> > > >
> > > > * Support for partial requests (i.e. AJAX). I imagine this would be
> > > > along the lines of standardising the request and response formats for
> > > > partial requests, and requiring a javascript implementation.
> > > >
> > > > * Ability to invoke actions on first page request. When you're linked
> > > > from other sites, or from a mail client you can't really expect them to
> > > > send the whole state of the component tree, which would be needed to
> > > > invoke an action from that tree (although this does work). Instead, you
> > > > might be able to create a new action listener type which is invoked when
> > > > the tree it is attached to is created/rendered. Of course, it'd have to
> > > > fit into the lifecycle somehow. A simple use case for this would be a
> > > > "click here to vote for struts" link in an email which should invoke a
> > > > JSF Action{Listener}. Currently you'd probably do this with a
> > > > PhaseListener or ServletFilter.
> > > >
> > > > * Ability to define converters for annotated classes (e.g. @Entity).
> > > > We can do <converter-for-class>, which also works for interfaces, but
> > > > there are cases where an annotation might indicate that a common
> > > > converter could be used. In the case of @Entity, you might be able to
> > > > use something like EntityManager.getId(entity).toString() to convert the
> > > > class (somebody add getId() to JPA 1.1 please!).
> > > >
> > > > * Ability to use #{foo} as an lvalue. Maybe more specific to the EL
> > > > spec, but ATM only #{foo.bar} can be used as an lvalue. Sometimes I just
> > > > want to keep a simple string in the session scope and do things like
> > > > <h:inputText value="#{foo}"/>, but instead I have to make a separate
> > > > bean just containing a String.
> > > >
> > > > * Reinvestigate, as per Jabob's ideas, whether we /really/ need
> > > > component state-saving. I got pretty confused when I wrote a simple
> > > > regexp validator that kept forgetting what the regexp was. It was all
> > > > there in the .xhtml file! That was until I learnt about state-saving
> > > > (which was more than I really wanted to know).
> > > >
> > > > * Dump JSP, and make facelets standard.
> > > >
> > > > Happy Oktoberfest!
> > > >
> > > > Roger
> > > >
> > > >
> > > > Martin Marinschek wrote:
> > > >> Hi there,
> > > >>
> > > >> Ed Burns, Jesse Alexander and me will be heading a discussion on what
> > > >> our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
> > > >> Munich, at the Oktoberfest.
> > > >>
> > > >> So it's a good opportunity for both talking about JSF and drinking
> > > >> beer - probably the best of the world. We'll meet up in:
> > > >>
> > > >> http://www.weisses-brauhaus.de/
> > > >>
> > > >> at 18:00
> > > >>
> > > >> and if you're interested in coming, reply to this mail and I'll
> > > >> include you in the reservation.
> > > >>
> > > >> regards,
> > > >>
> > > >> Martin
> > > >>
> > > >
> > > >
> > >
> > >
> > > --
> > > ----------------------------------------
> > > Ninth Avenue Software
> > > p: +61 7 3137 1351 (UTC +10)
> > > f: +61 7 3102 9141
> > > w: http://www.ninthavenue.com.au
> > > e: info@ninthavenue.com.au
> > > ----------------------------------------
> > >
> > >
> >
>
>
> --
> =============================
> Shinpei Ohtani
> shinpei.ohtani@gmail.com
> =============================
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Shinpei Ohtani <sh...@gmail.com>.
Hi,
> All I need is JSP definetely dropped, and a decent exception handling
> mechanism! :D
Yeah, I agree with you, tetsuo.
We need good exception handling mechanism.
2006/9/27, tetsuo <ro...@gmail.com>:
> All I need is JSP definetely dropped, and a decent exception handling
> mechanism! :D
>
> Have fun, guys!
>
>
> On 9/26/06, Roger Keays <ro...@ninthavenue.com.au> wrote:
> >
> > One more:
> >
> > * New listener for FacesServlet startup/shutdown. Some JSF
> > extensions may need to do some initial configuration on startup and
> > shutdown but these extensions can't add a ServletContextListener to
> > web.xml. ATM you can get similar behaviour by using a PhaseListener and
> > deregistering it after it is first run, but that is just a workaround
> > really.
> >
> > Roger Keays wrote:
> > >
> > > Hi Martin,
> > >
> > > Here are a couple of ideas I've jotted down:
> > >
> > > * Native support for conversation scope.
> > >
> > > * Support for partial requests (i.e. AJAX). I imagine this would be
> > > along the lines of standardising the request and response formats for
> > > partial requests, and requiring a javascript implementation.
> > >
> > > * Ability to invoke actions on first page request. When you're linked
> > > from other sites, or from a mail client you can't really expect them to
> > > send the whole state of the component tree, which would be needed to
> > > invoke an action from that tree (although this does work). Instead, you
> > > might be able to create a new action listener type which is invoked when
> > > the tree it is attached to is created/rendered. Of course, it'd have to
> > > fit into the lifecycle somehow. A simple use case for this would be a
> > > "click here to vote for struts" link in an email which should invoke a
> > > JSF Action{Listener}. Currently you'd probably do this with a
> > > PhaseListener or ServletFilter.
> > >
> > > * Ability to define converters for annotated classes (e.g. @Entity).
> > > We can do <converter-for-class>, which also works for interfaces, but
> > > there are cases where an annotation might indicate that a common
> > > converter could be used. In the case of @Entity, you might be able to
> > > use something like EntityManager.getId(entity).toString() to convert the
> > > class (somebody add getId() to JPA 1.1 please!).
> > >
> > > * Ability to use #{foo} as an lvalue. Maybe more specific to the EL
> > > spec, but ATM only #{foo.bar} can be used as an lvalue. Sometimes I just
> > > want to keep a simple string in the session scope and do things like
> > > <h:inputText value="#{foo}"/>, but instead I have to make a separate
> > > bean just containing a String.
> > >
> > > * Reinvestigate, as per Jabob's ideas, whether we /really/ need
> > > component state-saving. I got pretty confused when I wrote a simple
> > > regexp validator that kept forgetting what the regexp was. It was all
> > > there in the .xhtml file! That was until I learnt about state-saving
> > > (which was more than I really wanted to know).
> > >
> > > * Dump JSP, and make facelets standard.
> > >
> > > Happy Oktoberfest!
> > >
> > > Roger
> > >
> > >
> > > Martin Marinschek wrote:
> > >> Hi there,
> > >>
> > >> Ed Burns, Jesse Alexander and me will be heading a discussion on what
> > >> our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
> > >> Munich, at the Oktoberfest.
> > >>
> > >> So it's a good opportunity for both talking about JSF and drinking
> > >> beer - probably the best of the world. We'll meet up in:
> > >>
> > >> http://www.weisses-brauhaus.de/
> > >>
> > >> at 18:00
> > >>
> > >> and if you're interested in coming, reply to this mail and I'll
> > >> include you in the reservation.
> > >>
> > >> regards,
> > >>
> > >> Martin
> > >>
> > >
> > >
> >
> >
> > --
> > ----------------------------------------
> > Ninth Avenue Software
> > p: +61 7 3137 1351 (UTC +10)
> > f: +61 7 3102 9141
> > w: http://www.ninthavenue.com.au
> > e: info@ninthavenue.com.au
> > ----------------------------------------
> >
> >
>
--
=============================
Shinpei Ohtani
shinpei.ohtani@gmail.com
=============================
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by tetsuo <ro...@gmail.com>.
All I need is JSP definetely dropped, and a decent exception handling
mechanism! :D
Have fun, guys!
On 9/26/06, Roger Keays <ro...@ninthavenue.com.au> wrote:
>
> One more:
>
> * New listener for FacesServlet startup/shutdown. Some JSF
> extensions may need to do some initial configuration on startup and
> shutdown but these extensions can't add a ServletContextListener to
> web.xml. ATM you can get similar behaviour by using a PhaseListener and
> deregistering it after it is first run, but that is just a workaround
> really.
>
> Roger Keays wrote:
> >
> > Hi Martin,
> >
> > Here are a couple of ideas I've jotted down:
> >
> > * Native support for conversation scope.
> >
> > * Support for partial requests (i.e. AJAX). I imagine this would be
> > along the lines of standardising the request and response formats for
> > partial requests, and requiring a javascript implementation.
> >
> > * Ability to invoke actions on first page request. When you're linked
> > from other sites, or from a mail client you can't really expect them to
> > send the whole state of the component tree, which would be needed to
> > invoke an action from that tree (although this does work). Instead, you
> > might be able to create a new action listener type which is invoked when
> > the tree it is attached to is created/rendered. Of course, it'd have to
> > fit into the lifecycle somehow. A simple use case for this would be a
> > "click here to vote for struts" link in an email which should invoke a
> > JSF Action{Listener}. Currently you'd probably do this with a
> > PhaseListener or ServletFilter.
> >
> > * Ability to define converters for annotated classes (e.g. @Entity).
> > We can do <converter-for-class>, which also works for interfaces, but
> > there are cases where an annotation might indicate that a common
> > converter could be used. In the case of @Entity, you might be able to
> > use something like EntityManager.getId(entity).toString() to convert the
> > class (somebody add getId() to JPA 1.1 please!).
> >
> > * Ability to use #{foo} as an lvalue. Maybe more specific to the EL
> > spec, but ATM only #{foo.bar} can be used as an lvalue. Sometimes I just
> > want to keep a simple string in the session scope and do things like
> > <h:inputText value="#{foo}"/>, but instead I have to make a separate
> > bean just containing a String.
> >
> > * Reinvestigate, as per Jabob's ideas, whether we /really/ need
> > component state-saving. I got pretty confused when I wrote a simple
> > regexp validator that kept forgetting what the regexp was. It was all
> > there in the .xhtml file! That was until I learnt about state-saving
> > (which was more than I really wanted to know).
> >
> > * Dump JSP, and make facelets standard.
> >
> > Happy Oktoberfest!
> >
> > Roger
> >
> >
> > Martin Marinschek wrote:
> >> Hi there,
> >>
> >> Ed Burns, Jesse Alexander and me will be heading a discussion on what
> >> our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
> >> Munich, at the Oktoberfest.
> >>
> >> So it's a good opportunity for both talking about JSF and drinking
> >> beer - probably the best of the world. We'll meet up in:
> >>
> >> http://www.weisses-brauhaus.de/
> >>
> >> at 18:00
> >>
> >> and if you're interested in coming, reply to this mail and I'll
> >> include you in the reservation.
> >>
> >> regards,
> >>
> >> Martin
> >>
> >
> >
>
>
> --
> ----------------------------------------
> Ninth Avenue Software
> p: +61 7 3137 1351 (UTC +10)
> f: +61 7 3102 9141
> w: http://www.ninthavenue.com.au
> e: info@ninthavenue.com.au
> ----------------------------------------
>
>
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Roger Keays <ro...@ninthavenue.com.au>.
One more:
* New listener for FacesServlet startup/shutdown. Some JSF
extensions may need to do some initial configuration on startup and
shutdown but these extensions can't add a ServletContextListener to
web.xml. ATM you can get similar behaviour by using a PhaseListener and
deregistering it after it is first run, but that is just a workaround
really.
Roger Keays wrote:
>
> Hi Martin,
>
> Here are a couple of ideas I've jotted down:
>
> * Native support for conversation scope.
>
> * Support for partial requests (i.e. AJAX). I imagine this would be
> along the lines of standardising the request and response formats for
> partial requests, and requiring a javascript implementation.
>
> * Ability to invoke actions on first page request. When you're linked
> from other sites, or from a mail client you can't really expect them to
> send the whole state of the component tree, which would be needed to
> invoke an action from that tree (although this does work). Instead, you
> might be able to create a new action listener type which is invoked when
> the tree it is attached to is created/rendered. Of course, it'd have to
> fit into the lifecycle somehow. A simple use case for this would be a
> "click here to vote for struts" link in an email which should invoke a
> JSF Action{Listener}. Currently you'd probably do this with a
> PhaseListener or ServletFilter.
>
> * Ability to define converters for annotated classes (e.g. @Entity).
> We can do <converter-for-class>, which also works for interfaces, but
> there are cases where an annotation might indicate that a common
> converter could be used. In the case of @Entity, you might be able to
> use something like EntityManager.getId(entity).toString() to convert the
> class (somebody add getId() to JPA 1.1 please!).
>
> * Ability to use #{foo} as an lvalue. Maybe more specific to the EL
> spec, but ATM only #{foo.bar} can be used as an lvalue. Sometimes I just
> want to keep a simple string in the session scope and do things like
> <h:inputText value="#{foo}"/>, but instead I have to make a separate
> bean just containing a String.
>
> * Reinvestigate, as per Jabob's ideas, whether we /really/ need
> component state-saving. I got pretty confused when I wrote a simple
> regexp validator that kept forgetting what the regexp was. It was all
> there in the .xhtml file! That was until I learnt about state-saving
> (which was more than I really wanted to know).
>
> * Dump JSP, and make facelets standard.
>
> Happy Oktoberfest!
>
> Roger
>
>
> Martin Marinschek wrote:
>> Hi there,
>>
>> Ed Burns, Jesse Alexander and me will be heading a discussion on what
>> our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
>> Munich, at the Oktoberfest.
>>
>> So it's a good opportunity for both talking about JSF and drinking
>> beer - probably the best of the world. We'll meet up in:
>>
>> http://www.weisses-brauhaus.de/
>>
>> at 18:00
>>
>> and if you're interested in coming, reply to this mail and I'll
>> include you in the reservation.
>>
>> regards,
>>
>> Martin
>>
>
>
--
----------------------------------------
Ninth Avenue Software
p: +61 7 3137 1351 (UTC +10)
f: +61 7 3102 9141
w: http://www.ninthavenue.com.au
e: info@ninthavenue.com.au
----------------------------------------
Re: [OFFTOPIC] What I wish that JSF 2.0 would be like...
Posted by Roger Keays <ro...@ninthavenue.com.au>.
Hi Martin,
Here are a couple of ideas I've jotted down:
* Native support for conversation scope.
* Support for partial requests (i.e. AJAX). I imagine this would be
along the lines of standardising the request and response formats for
partial requests, and requiring a javascript implementation.
* Ability to invoke actions on first page request. When you're linked
from other sites, or from a mail client you can't really expect them to
send the whole state of the component tree, which would be needed to
invoke an action from that tree (although this does work). Instead, you
might be able to create a new action listener type which is invoked when
the tree it is attached to is created/rendered. Of course, it'd have to
fit into the lifecycle somehow. A simple use case for this would be a
"click here to vote for struts" link in an email which should invoke a
JSF Action{Listener}. Currently you'd probably do this with a
PhaseListener or ServletFilter.
* Ability to define converters for annotated classes (e.g. @Entity).
We can do <converter-for-class>, which also works for interfaces, but
there are cases where an annotation might indicate that a common
converter could be used. In the case of @Entity, you might be able to
use something like EntityManager.getId(entity).toString() to convert the
class (somebody add getId() to JPA 1.1 please!).
* Ability to use #{foo} as an lvalue. Maybe more specific to the EL
spec, but ATM only #{foo.bar} can be used as an lvalue. Sometimes I just
want to keep a simple string in the session scope and do things like
<h:inputText value="#{foo}"/>, but instead I have to make a separate
bean just containing a String.
* Reinvestigate, as per Jabob's ideas, whether we /really/ need
component state-saving. I got pretty confused when I wrote a simple
regexp validator that kept forgetting what the regexp was. It was all
there in the .xhtml file! That was until I learnt about state-saving
(which was more than I really wanted to know).
* Dump JSP, and make facelets standard.
Happy Oktoberfest!
Roger
Martin Marinschek wrote:
> Hi there,
>
> Ed Burns, Jesse Alexander and me will be heading a discussion on what
> our users dreamed JSF 2.0 would be like - on friday, 2006/09/29, in
> Munich, at the Oktoberfest.
>
> So it's a good opportunity for both talking about JSF and drinking
> beer - probably the best of the world. We'll meet up in:
>
> http://www.weisses-brauhaus.de/
>
> at 18:00
>
> and if you're interested in coming, reply to this mail and I'll
> include you in the reservation.
>
> regards,
>
> Martin
>
--
----------------------------------------
Ninth Avenue Software
p: +61 7 3137 1351 (UTC +10)
f: +61 7 3102 9141
w: http://www.ninthavenue.com.au
e: info@ninthavenue.com.au
----------------------------------------