[
https://issues.apache.org/jira/browse/OWB-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764325#comment-13764325
]
Tobias Stoeckmann commented on OWB-898:
---------------------------------------
The problem can be fixed by using another method name, of course. Also, it only
happens if the classes are in a scope, i.e. removing the @RequestScoped
annotation fixes the issue, too. It's the creation of a Proxy class (like
$$OwbNormalScopeProxy0) that triggers this issue.
> ClassFormatError in ASM engine
> ------------------------------
>
> Key: OWB-898
> URL: https://issues.apache.org/jira/browse/OWB-898
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Tobias Stoeckmann
> Labels: ASM, ClassFormatError, bug
> Attachments: cdi-blow.zip
>
>
> It is possible for OpenWebBeans to throw a ClassFormatError while
> constructing an instance of a class that "overrides" a package private method
> of a super class with an own package private method. Technically, the methods
> are not overriden, which leads to two methods with the same signature --
> therefore the FormatError.
> de.cewecolor.cdi.blow.sub.SuperClass#setValue(String)
> de.cewecolor.cdi.blow.SubClass#setValue(String) extends SuperClass
> BeanManager#getReference(SubClass.class) will throw an Error.
> Please see the attached example project, it's a very small example triggering
> the issue (standalone container).
> I assume that this problem is related to the switch to ASM. For one,
> OpenWebBeans 1.1.8 works fine and it can be seen here too:
> http://issues.gradle.org//browse/GRADLE-2695
> Tested also with 1.2.1-SNAPSHOT which uses ASM 4, still the same issue.
--
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
