Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
I ran into a deployment error of an ejblite bean because the bean implemented multiple interfaces. The bean actually only had one
interface. The second interface was dynamically added by new Aries weaving code. The interface is marked as synthetic. Ignoring synthetic interfaces would seem to be the best way to avoid this problem. Otherwise we'll need a mechanism to configure interfaces to be ignored (or add the Aries WeavingProxy interface to the list of interfaces we currently ignore...real