[
https://issues.jboss.org/browse/AS7-6041?page=com.atlassian.jira.plugin.s...
]
Jozef Hartinger commented on AS7-6041:
--------------------------------------
The problem here is that both the root resource and its decorator implement a
JAX-RS-annotated interface. As a result, RESTEasy registers both the resource class and
the decorator as resources. RESTEasy then tries to instantiate the abstract decorator
class.
A CDI decorator should never be registered as a JAX-RS resource, no matter if it's
abstract or not.
To reproduce, build the application above and visit
http://localhost:8080/restTest/rest/user
CDI Decorator for a JAX-RS annotated interface results in
WELD-001306
---------------------------------------------------------------------
Key: AS7-6041
URL:
https://issues.jboss.org/browse/AS7-6041
Project: Application Server 7
Issue Type: Bug
Components: REST
Affects Versions: 7.1.1.Final
Reporter: Daniel Sachse
Assignee: Stuart Douglas
Fix For: 7.2.0.Alpha1
I already bugged the Errai and Resteasy guys with my problem, but I was told that you
guys are in charge of this ;)
I possibly discovered a bug in the Weld implementation provided with JBoss 7.1.1.Final.
I was playing around with Errai and JAX-RS and I discovered that when I add the JAX-RS
annotations to the interface this works as expected.
As soon as I start to use a CDI Decorator with the JAX-RS interface, i start getting the
following error:
"org.jboss.weld.exceptions.UnproxyableResolutionException: WELD-001306 Attempting to
inject an unproxyable normal scoped bean Decorator….."
If I then put the JAX-RS annotations back at the implementation, everything works fine.
Unfortunately this behavior is not working for me, because Errai needs the annotations at
the interface to create client code.
As I was unsure if this only happened with Errai on the classpath, I created a very
little demo project, which exactly shows the bug I mentioned:
https://github.com/w0mbat/RESTTest
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira