[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-4031) JavassistInstrumentor throws ClassNotFoundException when scanning annotations

Clint Popetz (JIRA) jira-events at lists.jboss.org
Fri May 15 15:23:46 EDT 2009

     [ https://jira.jboss.org/jira/browse/JBSEAM-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clint Popetz closed JBSEAM-4031.

    Resolution: Done

This should be fixed by JBSEAM-4139.

> JavassistInstrumentor throws ClassNotFoundException when scanning annotations
> -----------------------------------------------------------------------------
>                 Key: JBSEAM-4031
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4031
>             Project: Seam
>          Issue Type: Bug
>          Components: Wicket
>            Reporter: Paul Mooney
>            Assignee: Clint Popetz
> A ClassNotFoundException is thrown when the javassistInstrumentor encounters annotations that are not in the classpath. This happens when :
> -Using the seam-instrument-wicket plugin
> -scanAnnotations is true
> -Classes that match the 'includes' patterns have a TYPE targetted annotation which is defined in the project, or in an artifact that is not a dependency of the plugin.
> This seems to happen because dependencies of the project, and the project's classes are not in the classpath of the seam-instrument-wicket plugin.
> Possible Solutions:
> 1. Somehow put all of the project's dependencies and classes in the plugin's classpath when it runs.
> or 
> 2. Replace all calls to 'CtClass.getAnnotations()' inside of JavassistInstrumentor with 'CtClass.getAvailableAnnotations()' which only loads Annotations on the classpath and does not throw a ClassNotFoundException.

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


More information about the seam-issues mailing list