TOBAGO: howto handle client side events (e.g. onchage) in t:selectManyCheckBox

Hi, I would like to handle onchage or onclick events in the client side. It seems missing from the Tobago tld. Is there away around this limitation? Is there a chance to get a fix for that? TIA Dani

RE: JSF Webflow support?

Hi, Do you have an estimation when to expect the first version? Also, does this mean we better not use shale dialog but rather wait for the spring webflow integration? Thanks, Dani From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig McClanahan Sent:

tobago and myfaces extensions in the same webapp

Hi, I would like to use Tobago components and myfaces extensions on the same jsf page. In particular x:panelNavigation, x:saveState and x:aliasBean. 15:55:04,578 ERROR [org.apache.myfaces.tobago.context.ResourceManager] Path not found, and no fallback. Using empty string. mainDirs

RE: x:inputCalendar bugs

I totally agree. The wrapper, API and tag also require improvements. See http://jscalendar.sourceforge.net it seems very robust and flexible. Contact them. Maybe they are willing to add another license in addition to LGPL. From: Martin Marinschek [mailto:[EMAIL PROTECTED]

x:inputCalendar flexibitly and interntionliztion missing features

When body had a dir=rtl month and year selection popup do no show up under their links. There is no way to replace the button, just the text on it. What if I want a picture? The least is to be able to assign a style and a styleClass to the button in popup

RE: OT: How do you intergrate a Jasper Report into a MYFaces app?

Glen, Leaving MyFaces out, do you know how to show it using a simple servlet/jsp application? If not, could you describe the use case and user interaction you want to use for generating a sample report? Dani From: Glenn Davidson [mailto:[EMAIL PROTECTED] Sent: Thursday,

RE: Serious inherent problem with the JSF framework life cycle and value binding handling?

+0200, Dani Kenan [EMAIL PROTECTED] wrote: It seems quite clear that change event handlers cannot be used together with value properties bound to request scope beans, since they will always be invoked. JSF promises to keep the expressions for all value binding expressions that you

RE: Serious inherent problem with the JSF framework life cycle and value binding handling?

+0200, Dani Kenan [EMAIL PROTECTED] wrote: -Original Message- From: Craig McClanahan [mailto:[EMAIL PROTECTED] Sent: Monday, February 07, 2005 3:01 AM To: MyFaces Discussion Cc: Sean Schofield Subject: Re: Serious inherent problem with the JSF framework life cycle

Serious inherent problem with the JSF framework life cycle and value binding handling?

Hi all, I think there are some serious inherent problem with the JSF framework life cycle and value binding handling. Here is an example how a ValueChangeEvent always gets fired, even w/o any changes: When the value property is bound to a request scoped managed bean field, e.g.:

RE: Serious inherent problem with the JSF framework life cycle and value binding handling?

of the scenarios you are describing. sean On Thu, 03 Feb 2005 13:12:15 +0200, Dani Kenan [EMAIL PROTECTED] wrote: Hi all, I think there are some serious inherent problem with the JSF framework life cycle and value binding handling. Here is an example how a ValueChangeEvent always