Re: [tobago] Validation in Popups

Hello Udo, thanks for the answer but my form is already around the tc:button which I used to open the popup. Here is a snippset of my original version. The popup works and the form data will processed. Only validations and required checks doesn't work. In case of missing or wrong data the pop

Re: commandbutton does not call the backend bean

Seems like the validation failed for some reason. Did you add a 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 : > Hi all, > > I'm using MyFaces 1.1.5 and Tomahawk 1.1.6 in an

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 : > Great! > > I guess the logger version mismatch causes a noclassdeffounderror or > something inside beanval. I guess we need to implement some additiona

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 lifec

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 > Thanks for your help. I solved the problem. After I

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 2010

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

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 objec

[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: What happens here is every time the checkbox is selected/deselected the listener method