[
https://jira.jboss.org/jira/browse/WELD-468?page=com.atlassian.jira.plugi...
]
Nicklas Karlsson commented on WELD-468:
---------------------------------------
Due to the fact that RIBeans cache the proxyable as a boolean and we don't want to tie
validation messages to the RIBean the process is split into two phases, the
"is"-phase which returns a boolean and a "getException"-phase. There
is no code duplication though as the "is" uses the "getException"
internally.
Not optimal perhaps but doesn't really matter since when the exception is thrown, the
"manure has already hit the AC system".
Weld should give better error message about why it can't proxy a
class
----------------------------------------------------------------------
Key: WELD-468
URL:
https://jira.jboss.org/jira/browse/WELD-468
Project: Weld
Issue Type: Bug
Components: Class Beans (Managed and Session), Producers (Methods, Fields and
Disposers)
Affects Versions: 1.0.1.Final
Reporter: Pete Muir
Assignee: Nicklas Karlsson
Priority: Minor
Fix For: 1.0.2.CR1
For a bean like
@Entity
@Named
@RequestScoped
public class Plot extends RObject {
...
}
we get an error like
Caused by: javax.enterprise.inject.UnproxyableResolutionException: Normal scoped bean
org.jboss.weld.bean-/home/ss141213/NetBeansProjects/ear1/dist/gfdeploy/ear1/ear1-ejb_jar/-ManagedBean-class
org.vgcowa.dm.Plot is not proxyable
which was caused by a final method.
Not a useful error message!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira