Constructor validation
by Gunnar Morling
Hi experts,
Emmanuel asked me to take the lead on the method validation feature,
so be prepared for related questions, API proposals and requests for
feedback via the mailing list :)
The first issue I'd like to discuss is the validation of constructor
arguments. Is this something which we want to support at all? I don't
think there are that many interception solutions which enable
constructor interception at all (for instance CDI interceptors don't,
AFAIK).
So personally I'd be fine with focussing on actual method validation
in BV 1.1, waiting for user demand for constructor validation and
adding it possibly in a later release. WDYT?
If we decide to include constructor validation, should we support the
validation of newly created objects (similar to return value
validation), e.g. like that:
public class Foo {
@Valid
public Foo() {
}
}
Here @Valid would trigger a validation of the newly instantiated Foo
object (whether to use @Valid or another annotation still needs to be
discussed). Any thoughts?
--Gunnar
14 years, 1 month
Java EE TCK version
by Matt Benson
Hi all,
As far as I know, the version of the JSR303 TCK still in use with
Java EE is 1.0.3.GA; i.e. that's what Geronimo and OpenEJB are both
constrained to use here on the Apache side of the fence. As you may
recall, there is a huge compatibility gap between 1.0.4.GA and
1.0.5.GA of the TCK due to
https://hibernate.onjira.com/browse/BVTCK-12 --as far as I know it's
impossible for an implementation of JSR303 to pass < 1.0.5.GA and >=
1.0.5.GA simultaneously. What is the procedure for upgrading the Bean
Validation TCK Oracle will use for Java EE, so that EE implementations
can use the latest JSR303 implementations?
Thanks,
Matt
14 years, 1 month
