Hi Gerhard,
thanx for quick response. I tracked down the problem that the Annotation
(@BeanValidation) is not available on objectToInspect.getClass() in
ExtValBeanValidationMetaDataInternals#transferGroupValidationInformationToFoundGroups.
objectToInspect.getClass() returns a bytecode enhanced
Update: It works when I use the @RequestScoped Annotation from javax.faces.bean
instead of javax.enterprise.context. In that case there is no byte code proxy
returned (objectToInspect.getClass()).
But anyways I expect that it should also run with the CDI scopes.
Manuel Gamerdinger
T-Systems
Hi Gerhard,
I created an issue. My further analysis showed that this is a bug and not an
improvement. The byte code proxy is correct. The @BeanValidation annotation is
not marked as @Inherited and therefore not populated to its subclasses. But the
proxy is a subclass.
So for me there are 2
Hi Gerhard,
no, we're using the standard WebSphere 8.0 stack which uses OpenWebBeans 1.1.0.
Anyways can you give me more information about the ProxyHelper?
Regards,
Manuel
-Ursprüngliche Nachricht-
Von: Gerhard Petracek [mailto:gerhard.petra...@gmail.com]
Gesendet: Freitag, 19.
Hi Gerhard,
ProxyUtils.getUnproxiedClass(objectToInspect.getClass()) works fine in my case.
But I think the bug is exactly in this while loop. In this loop always the
objectToInspect is passed to the
#transferGroupValidationInformationToFoundGroups. A second iteration will
result in same
Hello MyFaces ExtVal users,
I've a question regarding group validation together with @BeanValidation
annotation. In my example the @BeanValidation annotation only works on page
bean fields. On class level it seems that the annotation is ignored.
This works:
6 matches
Mail list logo