[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4434) Broken wicket instrumentation instructions for Ant

[Rob Shepherd (JIRA)]

    [ https://jira.jboss.org/browse/JBSEAM-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12531019#action_12531019 ] 

Rob Shepherd commented on JBSEAM-4434:
--------------------------------------

I ran into this too

http://seamframework.org/Community/BuildTimeWicketInstrumentationWithAntAndOtherProblems

Christians comments are correct - the classpath for the instrumentation task needs to include everything *including* the compiled classes it is instrumenting (I.e. the instrumentation "fileset" does not contribute towards the "classpath"


> Broken wicket instrumentation instructions for Ant
> --------------------------------------------------
>
>                 Key: JBSEAM-4434
>                 URL: https://jira.jboss.org/browse/JBSEAM-4434
>             Project: Seam
>          Issue Type: Bug
>          Components: Wicket
>    Affects Versions: 2.2.0.GA
>            Reporter: Christian Bauer
>            Assignee: Clint Popetz
>         Attachments: screenshot-1.jpg
>
>
> 1. The HTML documentation of the wicket chapter is broken, see attached screenshot.
> 2. The PDF documentation includes the following instructions for enhancing the Wicket components:
> <taskdef name="instrumentWicket" 
>    classname="org.jboss.seam.wicket.ioc.WicketInstrumentationTask"> 
>   <classpath>
>     <pathelement location="lib/jboss-seam-wicket-ant.jar"/> 
>     <pathelement location="web/WEB-INF/lib/jboss-seam-wicket.jar"/> 
>     <pathelement location="lib/javassist.jar"/> 
>     <pathelement location="lib/jboss-seam.jar"/> 
>   </classpath> 
> </taskdef> 
> <instrumentWicket outputDirectory="${build.instrumented}" useAnnotations="true"> 
>   <classpath refid="build.classpath"/> 
>   <fileset dir="${build.classes}" includes="**/*.class"/> 
> </instrumentWicket> 
> What is "build.classpath"?Nobody can look at the examples/wicket/build.xml and figure that one out either. So it's a total mystery why an additional classpath needs to be referenced within the task, when the task definition already lists all (you'd think) required classes. Users will not know what should be defined on that classpath.
> Without this classpath setting or with just guessing what could/should be on that classpath, you will get  "java.lang.RuntimeException: javassist.NotFoundException: HelloWorldApplication" (the only classes in build.classes are the ones for a Wicket HelloWorld, so this is just the first class file found).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira