Den 19.10.2010 10:06, skrev Emmanuel Bernard:
> Cross validation marker annotations like @ExactlyOneNull are not really
> actual constraints (ie annotated with @Constraint) because somehow they must
> carry two logic:
> - the property checking logic
> - the "aggregation" logic
> Besides the
Cross validation marker annotations like @ExactlyOneNull are not really actual
constraints (ie annotated with @Constraint) because somehow they must carry two
logic:
- the property checking logic
- the "aggregation" logic
Besides these markers should be ignored by the rest of the Bean Validatio
Ok now I see it.
Using groups for cross-validation is a very nice solution to be able to
reuse them on multiple sets of properties.
Then in Emmanuel's example I guess it should be
@AtLeastOneNotNullAmongst(groups={Group1.class,Group2.class})
B getB() { ... };
The @CrossValidation annotation at
I was also thinking about a generic class level @CrossValidation
constraint. I think Emmanuel and I
are thinking about the same thing here:
@CrossValidations({
@CrossValidation(forGroup=BankAccount.class),
@CrossValidation(forGroup=ContactDetails.class)
})
public class BankAccountNumber
On 16 oct. 2010, at 10:56, Dag Hovland wrote:
> On 15/10/10 13:33, Emmanuel Bernard wrote:
> (...)
>> That being said, I wonder whether you can write your approach atop a generic
>> class-level constraint @CrossValidation that would look for the properties
>> annotations and behave as expected.
On 15/10/10 13:33, Emmanuel Bernard wrote:
(...)
> That being said, I wonder whether you can write your approach atop a generic
> class-level constraint @CrossValidation that would look for the properties
> annotations and behave as expected. That would be a nice way to offer both
> world to the
Hi,
I'm quite late in the game but I finally had a chance to look at your main paper
http://www.ii.uib.no/publikasjoner/texrap/pdf/2009-389.pdf
I quite like your approach for boolean composition. It is very elegant and can
easily be added in a non breaking way to Hibernate Validator and Bean
Val
Yes, I completely agree, I didn't mean to suggest to actually replace
the annotations with internal code, but only that in this case the
advantage
of using annotations is reduced to the simple decoupling of validation
code form the rest, as it can be obtained with an XML configuration
file. A
On Wed, 06 Oct 2010 17:53:38 +0200, Federico Mancini
wrote:
> Class level validation is something we had considered as well, but
> discarded it as we considered it in a way "cheating" in our settings.
> This because what actually happens, if I understood correctly, is that
> the whole objec
Hi,
I just wanted to make a remark on the the difference between the class
level validation
in the jsr 303 and our cross-annotations, since I would like to hear
your opinion on the matter (that you probably have already discussed).
Class level validation is something we had considered as well,
Hi,
Help and contributions are always welcome :)
I recommend you start with this page
http://community.jboss.org/wiki/ContributingtoHibernateValidator
It contains information on where and how to check out the source and how
to built the project.
Once you have a local checkout and made yourse
Hi and thank you for your answer.
I am aware that our work is extremely similar to the jsr 303,
and that is exactly why I wanted to show it to you.
It just happened that we independently developed similar solutions for
the same problem, but
when we saw the specs for the jsr 303, we realized tha
Hi Frederico,
sorry for the late reply. I finally had some time to read through your
paper.
I think there are strong similarities between you work and Hibernate
Validator or
more specific the Bean Validation specification (JSR 303).
Property validation in the SHIP Validator is basically the s
Hi again,
I was just wondering whether I should interpret the lack of answers as
"no, this is not interesting at all", or as "we have a lot of other
things to do and do not have time for this right now"?
Federico
Den 22.09.2010 09:08, skrev Federico Mancini:
>Hi all,
> I am new to the lis
14 matches
Mail list logo
