[Trinidad} Issue with ValueChangeListener

Hi, We are using Trinidad 1.2 with facelets.There are multiple checkboxes in our form and we require to call an ActionListener every time a checkbox is selected/deselected. Below is the code: tr:form tr:selectBooleanCheckbox autoSubmit=true id=quantity1

Re: [Trinidad} Issue with ValueChangeListener

Hi, What's the scope of the bean ? If it's a request bean, then this is normal... Otherwise, the valueChangeListener is not called until the new value differs from the old one. Try to put a breakpoint in simpleBackingBean.processValueChange and compare old and new value as given in the event

Re: [tobago] Validation in Popups

Hello Michael, please try to put the form outside of the command tag, which opens the popup. This should solve your problems. The background is: The popup must be inside the form to consider it was already active. Regards, Udo Am 23.09.10 22:29, schrieb Michael Kakuschky: Hello, I have

AW: Bean Validation (JSR 303)

Thanks for your help. I solved the problem. After I fixed a version mismatch in SLF4J Bean Validation was enabled. Maybe the initialization checks the logger? Regards -Ursprüngliche Nachricht- Von: Jan-Kees van Andel [mailto:jankeesvanan...@gmail.com] Gesendet: Montag, 27. September

Re: Bean Validation (JSR 303)

Great! I guess the logger version mismatch causes a noclassdeffounderror or something inside beanval. I guess we need to implement some additional logging inside myfaces to debug such issues... Regards, Jan-Kees 2010/9/28 Matthias Niehoff niehoff.matth...@googlemail.com Thanks for your help.

commandbutton does not call the backend bean

Hi all, I'm using MyFaces 1.1.5 and Tomahawk 1.1.6 in an application and got a problem with a button. When I clicked the button, it did not call the backend bean but stayed in the same page. I noticed the lines below in the log file. org.apache.myfaces.lifecycle.LifecycleImpl - exiting from

Re: Bean Validation (JSR 303)

Great to hear! +1 on the additional logging if bean validation is there but fails to initialize! Regards, Jakob 2010/9/28 Jan-Kees van Andel jankeesvanan...@gmail.com: Great! I guess the logger version mismatch causes a noclassdeffounderror or something inside beanval. I guess we need to

Re: commandbutton does not call the backend bean

Seems like the validation failed for some reason. Did you add a h:messages to the page? You could also try to skip the model update (and valdiation) by setting the immediate attribute of the button to true. Christian 2010/9/28, Xiaobo Yang xiaobo.y...@gmail.com: Hi all, I'm using MyFaces