[jboss-jira] [JBoss JIRA] (WFLY-12614) Duplicated ConstraintViolation message

[Ronald Sigal (Jira)]

    [ https://issues.jboss.org/browse/WFLY-12614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798320#comment-13798320 ] 

Ronald Sigal commented on WFLY-12614:
-------------------------------------

Well, it's a minor variation of a problem I fixed for https://issues.jboss.org/browse/RESTEASY-1749. One of the differences is that I handled the problem for CDI proxies, and the attached test case runs with EJB proxies. 

1. I can fix it, but when I try to turn the test case into an Aquillian test for the RESTEasy testsuite, I'm getting CDI proxies. When I turn off CDI in beans.xml, I'm getting POJOs. [~brian.stansberry], do you know how to force the creation of EJB proxies?

2. Another issue: I'm detecting CDI proxies using Classs.isSynthetic(), but it doesn't work for EJB proxies. I can test for classname.contains("$$$view"), but that seems awfully implementation dependent. Do you know a better way?

Thanks.

> Duplicated ConstraintViolation message
> --------------------------------------
>
>                 Key: WFLY-12614
>                 URL: https://issues.jboss.org/browse/WFLY-12614
>             Project: WildFly
>          Issue Type: Bug
>          Components: Bean Validation, REST
>    Affects Versions: 17.0.1.Final, 18.0.0.Beta1
>            Reporter: Robin Schimpf
>            Assignee: Alessio Soldano
>            Priority: Major
>         Attachments: wildfly-bug.zip
>
>
> We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request.
> Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now.
> I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)