FacesClient Components [Was Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])]

2004-11-04 Thread dhay
elopers List <[EMAIL PROTECTED]>, Martin Cooper <[EMAIL PROTECTED]> | | cc: | | Subject: Re: JSF and highly dynamic apps (was Re: Struts-B

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-11-04 Thread Craig McClanahan
On Tue, 2 Nov 2004 21:43:41 -0800, Martin Cooper <[EMAIL PROTECTED]> wrote: > This is a really interesting statement. Perhaps I'm wrong, but I've > always thought the whole point of JSF was visual components. Yet the > statement above clearly indicates that JSF goes well beyond that > charter, and

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-11-04 Thread Craig McClanahan
In order to meet the spec requirements for handling server side events related to the view tier components, JSF also provides a front controller responsible for handling the server side request processing lifecycle, with event listeners and other plug-in points for either application code or contro

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-11-03 Thread Michael Rasmussen
> statement above clearly indicates that JSF goes well beyond that > charter, and clearly suggests that there are facets of JSF that should > not be a part of that JSR. > >From the original design goals of JSR 127 (JSF) "Provide a JavaBeans model for dispatching events from client-side GUI contro

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-11-02 Thread Martin Cooper
On Sun, 31 Oct 2004 23:00:41 -0700, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On Sun, 31 Oct 2004 21:30:22 -0600, Eddie Bush <[EMAIL PROTECTED]> wrote: > > > > Unless Martin is incorrect about the way JSF handles requests, I'm inclined > > to believe (despite the fact JSF will be a part of the

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-10-31 Thread Craig McClanahan
On Sun, 31 Oct 2004 21:30:22 -0600, Eddie Bush <[EMAIL PROTECTED]> wrote: > > Unless Martin is incorrect about the way JSF handles requests, I'm inclined > to believe (despite the fact JSF will be a part of the next specification) > we might want to consider using something else under the covers i

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-10-31 Thread Eddie Bush
ist" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, October 31, 2004 7:03 PM Subject: Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]]) Martin, you make an interesting comment that I thi

Re: JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-10-31 Thread Frank W. Zammetti
Martin, you make an interesting comment that I think ties into this discussion (loosely ;) ) that is worth mentioning... A lot of the tools us architects and developers use these days really only make sense in cases where you have a separation of activities in terms of page authors and develope

JSF and highly dynamic apps (was Re: Struts-BSF, Struts-Scripting [was Re: Proposal: Javascript-to-Java object conversions]]])

2004-10-31 Thread Martin Cooper
I hear what you're saying, Craig. However, I still feel that JSF doesn't buy me much when building highly dynamic apps. Some points to consider: * Since one of the goals of such apps is to minimise the number of full page refreshes, relatively little of the app can be constructed using tools such