[
http://opensource.atlassian.com/projects/hibernate/browse/HV-482?page=com...
]
Tim Canavan edited comment on HV-482 at 6/6/11 5:20 PM:
--------------------------------------------------------
Thanks for the reply
We are using method validation through a MethodInterceptor for the service methods. We are
using the exact same interceptor for the unit tests
and applying it to exactly the same service methods. All parameter validation is at the
interface level.
So it works for OpenEJB and not for Weblogic.
Our interceptor works fine with beta1 where the ConstraintDeclarationException is not
thrown. We need to solve this as
without a fix we cannot update to future versions ofthe HV
Tim
was (Author: tcanavan):
Thanks for the reply
We are using method validation through a MethodInterceptor for the servicde methods. We
are using the exact same interceptor for the unit tests
and applying it to exactly the same service methods. All parameter validation is at the
interface level.
So it works for OpenEJB and not for Weblogic.
Our interceptor works fine with beta1 where the ConstraintDeclarationException is not
thrown. We need to solve this as
without a fix we cannot update to future versions ofthe HV
Tim
Weblogic ConstrantDeclationException HVbeta2
--------------------------------------------
Key: HV-482
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HV-482
Project: Hibernate Validator
Issue Type: Bug
Affects Versions: 4.2.0.Beta2
Environment: Weblogic 10.3
Reporter: Tim Canavan
After upgrading to HV beta2 and changing all our validations to be at the interface
level
we get the constraint declaration exception
Caused by: javax.validation.ConstraintDeclarationException: Only the root method of an
overridden method in an inheritance hierarchy may be annotated with parameter constraints.
The following method itself has no parameter constraints but it is not defined on a
sub-type of class
Under OpenEJB which our unit tests use everything works fine.
Is there any code that HV could use that would allow it to understand these proxies or
would an option be available
to turn the check off.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira