probity wrote:

Karsten will probably answer you here but they have a mailing list to
ask questions about that product: users@validation.dev.java.net

https://validation.dev.java.net/servlets/ProjectMailingListList

Thanks in Advance...
IchBin, Pocono Lake, Pa, USA
http://weconsultants.servebeer.com/JHackerAppManager
__________________________________________________________________________

'If there is one, Knowledge is the "Fountain of Youth"'
-William E. Taylor,  Regular Guy (1952-)

   I'm not familiar with JGoodies, but Hibernate has a way around this: In
Hibernate, you can make the constructor private, so that client code will
know they shouldn't touch that constructor, but Hibernate will use
reflection to gain access to the constructor for its own internal use.

   If JGoodies has a similar capability, maybe you could use private
constructs to gain the benefits of the JGoodies framework without breaking
your design? Otherwise, perhaps you could submit this as a feature request
to the developers of JGoodies?

   - Oliver

The JGoodies Binding can work with POJOs. It does not require
to work with Java Beans, or even with Java Bean-like objects.
More generally, it can bind every observable read-write target,
where the read/write/observable are all optional. The Binding
has been designed around the ValueModel interface that describes
the latter.

Anyway, there are good reasons to not use an automatic databinding.

Yes, the JGoodies Validation can be used without the Binding.
The core library does not refer to any other JGoodies library.
In the Validation tutorial, the Binding just helped me save
boilerplate code necessary to bind the UI components to the
example domain values. And the Binding makes it quite easy
to validate on key typed, and focus lost.

If you want to validate on commit, here's one approach.
First commit the GUI state to your domain POJO properties;
then have a Validator for each domain object that you
want to validate, or have a Validator for the whole
domain object graph; then invoke the validator's #validate
method to get a ValidationResult. You can display this
result - if any - in a modal dialog. Or you can set
the result in a ValidationResultModel that will update
validation result views bound to that model.

Recently I added a Validation issue where you can track
the progress of "Add an example that doesn't use the Binding":
https://validation.dev.java.net/issues/show_bug.cgi?id=16

Please post further questions to the Validation user mailing list.

Kind regards,
Karsten Lentzsch