]
Grzegorz Demecki updated WFLY-4619:
-----------------------------------
Workaround Description:
Switching to xml approach: {{META-INF/validation.xml}} and removing validation
configuration (mainly custom constraint mapping) from my custom {{@Provider}} class (I
mean {{resteasy.bug.showcase.ValidationConfigurationContextResolver}}) causes the bug to
disappear. Validation is then performed correctly.
was:
Switching to xml approach: {{META-INF/validation.xml}} and removing configuration from my
custom {{@Provider}} class:
{{resteasy.bug.showcase.ValidationConfigurationContextResolver}} causes bug to disappear.
Custom ConstraintValidator for existing Constraint causes
{{javax.validation.UnexpectedTypeException: HV000030: No validator could be found for
type...}}
---------------------------------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-4619
URL:
https://issues.jboss.org/browse/WFLY-4619
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, REST
Affects Versions: 8.1.0.Final, 8.2.0.Final
Environment: * JDK 1.7.0_75
* Windows 7 Enterprise
* Deployed under Eclipse Luna Release (4.4.0) Build id: 20140612-0600
Reporter: Grzegorz Demecki
Assignee: Stuart Douglas
Labels: cdi, resteasy, validation
Attachments: test.zip
See attached sample, small project.
Bug is about using built-in {{(a)javax.validation.constraints.Min}} constraint annotation
for validating my custom type: {{resteasy.bug.showcase.params.IntParam}} when configuring
validation within {{@Provider}} class.