Qeustions about SortedSet and ListMultipleChoice (with and without Metagen)

In my project, for business reasons, we have classes with SortedSet members. The classes and their elements are all Serializable. I'm having trouble working with a SortedSetMantechControl object; when I try creating a ListMultipleChoiceMantechControl object for it (and putting it into a

RE: ValidationForm.addPropertyValidators sometimes looks for child properties in parent's model

Igorbut you can create a testcase, reproducing the bare bits of code in a testcase just like you did in the email below. the advantage would be that i would have something i can play with which makes it much easier to find the problem. I will work on a quick start tonight, when I'm not at work.

Added issue for assertFeedback

I've just submitted issue WICKET-4246 for the problem I found where WicketTester.assertFeedback required the actual feedback messages to be the expected messages in their exact order. Since the ftlines validation project through the Hibernate validator project returns messages in an unspecified

RE: ValidationForm.addPropertyValidators sometimes looks for child properties in parent's model

Dear Igor, (me) I get a call with expression being child, and target being the local test object.  Were expression parent.child, this would succeed, as it would call getParent().getChild(). However, I'm not sure whether this is my bug or the wicket-validation-bean library's. (Igor)this is

Metagen configuration issue

I've cut and pasted the Metagen configuration listed in https://github.com/42Lines/metagen into my project pom, and these declarations are generating the metamodels twice: in target/generated-sources/annotations, and in target/metamodel. What must I do to cut out one of the metamodel

RE: Metagen configuration issue

From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Friday, November 18, 2011 2:21 PM To: users@wicket.apache.org Subject: Re: Metagen configuration issue try removing the configuration block of the maven-processor-plugin and change the source location of the helper plugin to

RE: Metagen configuration issue

-Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Friday, November 18, 2011 2:43 PM To: users@wicket.apache.org Subject: Re: Metagen configuration issue very strange. we are using the configuration on the github page and its working great here. try using

RE: Metagen configuration issue

-Original Message- From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com] Sent: Friday, November 18, 2011 4:04 PM To: users@wicket.apache.org Subject: Re: Metagen configuration issue sweet, thanks. i will add it to the readme -igor plugin        

Debugging a NPE from a ModelPropertyResolver

I am trying to use Igor's wicket-validation-bean project, and I've managed to make a mistake where I'm getting a NullPointerException from when ValidationForm attempts to add property validators. Unfortunately, I can't tell what property it's trying to attach validators for here, as the

ValidationForm.addPropertyValidators sometimes looks for child properties in parent's model

I have some model classes with JSR 303 validation annotations, and I have some FormComponentPanels for each. Some of these will be nested. To test that the Wicket validation is correct, I'm creating a ValidationForm, which contains one of my panels, which contains another of my panels, and I am

RE: Debugging a NPE from a ModelPropertyResolver

No, we are using only the stock models, I think. In any case, the particular test class uses CompoundPropertyModel. From: Igor Vaynberg [igor.vaynb...@gmail.com] Sent: Thursday, November 17, 2011 7:24 PM To: users@wicket.apache.org Subject: Re: Debugging a

Configuration problem with net.ftlines.wicket-bean-validation

First, let me thank Igor Vaynberg for being so responsive updating the net.ftlines.wicket-bean-validationhttp://mvnrepository.com/artifact/net.ftlines.wicket-bean-validation project. I still have one final problem configuring it. I have a test that checks that setting a field to a value that

RE: Configuration problem with net.ftlines.wicket-bean-validation

From: Martin Grigorov [mailto:mgrigo...@apache.org] Hi, Looking at the stacktrace I think you should add this line to Wicket's resource bundle. Just add it to YourApplication.properties and it should be fine. That must be it. The library project tries to get its validation messages via the

RE: Configuration problem with net.ftlines.wicket-bean-validation

From: Martin Grigorov [mailto:mgrigo...@apache.org] Hi, Looking at the stacktrace I think you should add this line to Wicket's resource bundle. Just add it to YourApplication.properties and it should be fine. I'm a lot closer to fine, now. However, I think I've exposed a usability problem

WicketStuff JSR-303 validation breaks in WicketTester

I'm trying to use the wicketstuff.org JSR-303 validation project to use Hibernate Validator in my newish Wicket project. I have a FormComponentPanel with a model object set up for JSR-303 validation, but we are using vanilla Wicket Validators for it. To test the FormComponentPanel, I wrote a

RE: WicketStuff JSR-303 validation breaks in WicketTester

I took your advice and I am trying to use this project. I have some teething pains. See https://github.com/42Lines/wicket-bean-validation http://repo1.maven.org/maven2/net/ftlines/wicket-bean-validation/ I removed the wicketstuff.org jsr303 repository and added the ftlines one. I also noticed