-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
If a bean implements an interface designated as @Local (or @Remote) and it extends a base which implements the same interface, the interface is reported multiple times. Thus the ProxyFactory fails to start.
...
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:370)
at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.init(BaseStatefulProxyFactory.java:93)
at org.jboss.ejb3.stateful.BaseStatefulProxyFactory.start(BaseStatefulProxyFactory.java:99)
at org.jboss.ejb3.stateful.StatefulLocalProxyFactory.start(StatefulLocalProxyFactory.java:93)
at org.jboss.ejb3.session.ProxyDeployer.start(ProxyDeployer.java:90)
at org.jboss.ejb3.session.SessionContainer.start(SessionContainer.java:211)
at org.jboss.ejb3.stateful.StatefulContainer.start(StatefulContainer.java:140)
- blocks
-
JBPAPP-1601 Migrate EJBTHREE-1122 - Bean with multiple definitions of the same @Local or @Remote interface fails to deploy
- Resolved
- is related to
-
EJBTHREE-1123 Determining the messagingType of a MDB considers too many interfaces
- Closed
-
EJBTHREE-1124 Default business interface is incorrectly determined
- Closed
- relates to
-
EJBTHREE-785 Local interface implemented by superclass
- Closed