Ant building error

[Richard Broersma]

I'm trying for first attempt at building a WAR file using ANT. While following the instructions, I'm getting an error that indications to me that the classpath isn't being set to see the javaee.jar.

C:\Documents and Settings\rbroersma\java\bee>ant
Buildfile: C:\Documents and Settings\rbroersma\java\bee\build.xml

init:

initdirs:

compile:
    [javac] C:\Documents and Settings\rbroersma\java\bee\build.xml:19: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to
 false for repeatable builds
    [javac] Compiling 1 source file to C:\Documents and Settings\rbroersma\java\bee\build\classes
    [javac] C:\Documents and Settings\rbroersma\java\bee\src\java\com\javaranch\drive\BeeServlet.java:4: package javax.servlet.http does not exist
    [javac] import javax.servlet.http.*;
    [javac] ^
    [javac] C:\Documents and Settings\rbroersma\java\bee\src\java\com\javaranch\drive\BeeServlet.java:6: cannot find symbol
    [javac] symbol: class HttpServlet
    [javac] public class BeeServlet extends HttpServlet
    [javac]                                 ^
    [javac] C:\Documents and Settings\rbroersma\java\bee\src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol
    [javac] symbol  : class HttpServletRequest
    [javac] location: class com.javaranch.drive.BeeServlet
    [javac]     public void doGet( HttpServletRequest request, HttpServletResponse response )
    [javac]                        ^
    [javac] C:\Documents and Settings\rbroersma\java\bee\src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol
    [javac] symbol  : class HttpServletResponse
    [javac] location: class com.javaranch.drive.BeeServlet
    [javac]     public void doGet( HttpServletRequest request, HttpServletResponse response )
    [javac]                                                    ^
    [javac] 4 errors

BUILD FAILED
C:\Documents and Settings\rbroersma\java\bee\build.xml:19: Compile failed; see the compiler error output for details.

Total time: 2 seconds

However, when I check the location where I was instructed to place the javaee.jar file, I see that it is there.

>tree
Folder PATH listing
Volume serial number is 0006EFC4 0496:6E97
C:.
+---build
¦   +---classes
¦   +---dist
+---lib
¦   +---development
¦   +---production
+---src
    +---java
    ¦   +---com
    ¦       +---javaranch
    ¦           +---drive
    +---web

>dir lib\development\
 Volume in drive C has no label.
 Volume Serial Number is 0496-6E97

 Directory of C:\Documents and Settings\rbroersma\java\bee\lib\development

03/30/2011  10:34 AM    <DIR>          .
03/30/2011  10:34 AM    <DIR>          ..
03/15/2011  08:02 AM             2,822 javaee.jar

Does anyone have any thoughts about we my problem is?

The following is the build.xml contents:

<project name='bee' default='build' basedir='.'> <target name='init'> <property file='${user.home}/build.properties'/> <property name='app.name' value='${ant.project.name}'/> <property name='src.dir' location='src'/> <property name='lib.dir' location='lib'/> <property name='build.dir' location='build'/> <property name='classes.dir' location='${build.dir}/classes'/> <property name='dist.dir' location='${build.dir}/dist'/> </target> <target name='initdirs' depends='init'> <mkdir dir='${classes.dir}'/> <mkdir dir='${dist.dir}'/> </target> <target name='compile' depends='initdirs'> <javac srcdir='${src.dir}/java' destdir='${classes.dir}'> <classpath> <fileset dir='${lib.dir}/development' includes='javaee.jar'/> <fileset dir='${lib.dir}/production' includes='jr.jar'/> </classpath> </javac> </target> <target name='war' depends='compile'> <war destFile='${dist.dir}/${app.name}.war' webxml='${src.dir}/web/WEB-INF/web.xml'> <classes dir='${classes.dir}'/> <zipfileset dir='${lib.dir}/production' includes='jr.jar' prefix='WEB-INF/lib' /> <fileset dir='${src.dir}/web' excludes='WEB-INF/web.xml' /> </war> </target> <target name='build' depends='war' description='compile and create the war' /> <target name='clean' depends='init' description='Use for a clean build'> <delete dir='${build.dir}' /> </target> <target name='ffbuild' depends='clean, build' description='clean and create the war'/> <target name='deploy' depends='initdirs' description='copy the war file to the app server'> <delete verbose='true' dir='${deploy.dir}/${app.name}'/> <delete verbose='true' dir='${deploy.dir}/../application-deployments/default/${app.name}'/> <delete verbose='true' file='${deploy.dir}/${app.name}.war' /> <fail unless='deploy.dir' message='build.properties must exist in your home directory and define deploy.dir' /> <copy todir='${deploy.dir}' file='${dist.dir}/${app.name}.war'/> </target> </project>

[Carol Murphy]

I checked your build.xml against mine, and I see a naming difference for the j2ee.jar file. Where your file is named javaee.jar, I have a file named j2ee.jar. Maybe the name of the file has something to do with it?

[Carol Murphy]

Uhh, forgive me for asking, but did you put javaee.jar in your Classpath?

[Richard Broersma]

Carol Murphy wrote:Where your file is named javaee.jar, I have a file named j2ee.jar. Maybe the name of the file has something to do with it?

It could be, but the name in the ant script matches the name of the jar file on the file system. So I hope it would see it correctly.

Carol Murphy wrote:Uhh, forgive me for asking, but did you put javaee.jar in your Classpath?

I don't have the classpath variable set as an environment variable. When calling java or javac I specify the classpath using the -cp flag. However, I didn't see a way to supply the classpath at the command line when call the ant script.

I'm not an expert at ant scripts, but I thought ant would find the appropriate file classpath from my understanding of this ant script code snippet:
<target name='compile' depends='initdirs'> <javac srcdir='${src.dir}/java' destdir='${classes.dir}'> <classpath> <fileset dir='${lib.dir}/development' includes='javaee.jar'/> <fileset dir='${lib.dir}/production' includes='jr.jar'/> </classpath> </javac> </target>

[Carol Murphy]

The following is copied from the Cattle Drive instructions for Servlets:

Download the J2EE SDK(Java 2 Enterprise Edition Software Development Kit) from Sun, and install it. It is a supplement to the JDK you already have installed. You need to include the javaee.jar in your classpath.

You may need to add javvee.jar to your classpath variable.

[Richard Broersma]

Carol Murphy wrote:Download the J2EE SDK(Java 2 Enterprise Edition Software Development Kit) from Sun, and install it. It is a supplement to the JDK you already have installed.

When I go to the link for Enterprise Edition Software Development Kit I see that they only have J6EE rather than J2EE. I hope that's okay. I do know that when manually complying these files use JAVAC with the appropriately supplied -cp parameter, the compile is successful. It's only ANT that is having a hard time complying and not seeing javaee.jar.

Carol Murphy wrote:You need to include the javaee.jar in your classpath. ... You may need to add javvee.jar to your classpath variable.

Do you mean setting it as an environment variable? When reading the ANT documentation, it mentions that the CLASSPATH should be left unset as mentioned in the Windows Note:.

[Carol Murphy]

Grasping at straws here, but did you look inside the copy of javaee.jar inside of your app to verify that it contains the files that ANT can't locate? Maybe the jar file was corrupted somehow?

[Richard Broersma]

Grasping at straws here, but did you look inside the copy of javaee.jar inside of your app to verify that it contains the files that ANT can't locate? Maybe the jar file was corrupted somehow?

I was able to verify that the javaee.jar file is good. I spent some time to familiarize myself with ANT and I discovered some interesting things about this problem. I used the

ANT -debug

command, which produced all of the options that ANT was passing to javac. When I manually constructed these options for this compilation I get the same error that ANT does:

>javac -g -d .\build\classes -cp "C:\Documents and Settings\rbroersma\java\bee\build\classes;C:\Documents and Settings\rbroersma\java\bee\lib\development\javaee.jar;C:\Documents and Settings\rbroersma\java\bee\lib\production\jr.jar" -sourcepath "C:\Documents and Settings\rbroersma\java\bee\src\java" src\java\com\javaranch\drive\BeeServlet.java
src\java\com\javaranch\drive\BeeServlet.java:4: package javax.servlet.http does not exist
import javax.servlet.http.*;
^
src\java\com\javaranch\drive\BeeServlet.java:6: cannot find symbol
symbol: class HttpServlet
public class BeeServlet extends HttpServlet
                                ^
src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol
symbol  : class HttpServletRequest
location: class com.javaranch.drive.BeeServlet
    public void doGet( HttpServletRequest request, HttpServletResponse response )
                       ^
src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol
symbol  : class HttpServletResponse
location: class com.javaranch.drive.BeeServlet
    public void doGet( HttpServletRequest request, HttpServletResponse response )
                                                   ^
4 errors

>

However, if I change the -classpath to point to my glassfish installation of javaee.jar it compiles correctly.

>javac -g -d .\build\classes -cp "C:\Documents and Settings\rbroersma\java\bee\build\classes;C:\glassfish3\glassfish\lib\javaee.jar;C:\Documents and Settings\rbroersma\java\bee\lib\production\jr.jar" -sourcepath "C:\Documents and Settings\rbroersma\java\bee\src\java" src\java\com\javaranch\drive\BeeServlet.java

>

Since the javaee.jar in my lib dir is a direct (and repeated refreshed) copy of the javaee.jar in the glassfish lib directory, I suspect there is another reason why the compilation is failing. Could it be the modern versions of javaee.jar rely on peer jar file in the glashfish lib directory?

Any thoughts?

[Carol Murphy]

Way over my pay grade. What else do you have in the glassfish\lib directory that isn't in the java\bee\lib\development directory?

[Jaikiran Pai]

Richard Broersma wrote:command, which produced all of the options that ANT was passing to javac. When I manually constructed these options for this compilation I get the same error that ANT does:

>javac -g -d .\build\classes -cp "C:\Documents and Settings\rbroersma\java\bee\build\classes;C:\Documents and Settings\rbroersma\java\bee\lib\development\javaee.jar;C:\Documents and Settings\rbroersma\java\bee\lib\production\jr.jar" -sourcepath "C:\Documents and Settings\rbroersma\java\bee\src\java" src\java\com\javaranch\drive\BeeServlet.java
src\java\com\javaranch\drive\BeeServlet.java:4: package javax.servlet.http does not exist
import javax.servlet.http.*;
^
src\java\com\javaranch\drive\BeeServlet.java:6: cannot find symbol
symbol: class HttpServlet
public class BeeServlet extends HttpServlet
                                ^
src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol
symbol  : class HttpServletRequest
location: class com.javaranch.drive.BeeServlet
    public void doGet( HttpServletRequest request, HttpServletResponse response )
                       ^
src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol
symbol  : class HttpServletResponse
location: class com.javaranch.drive.BeeServlet
    public void doGet( HttpServletRequest request, HttpServletResponse response )
                                                   ^
4 errors

>

Having Java programs or jars in a folder containing spaces in its path isn't recommended. So try moving out your program and the jars from C:\Documents and Settings\rbroersma to maybe C:\rbroersma.

[Richard Broersma]

I copied the bee folder upto the root directory. Now there are no spaces in the classpath. It looks like I'm still getting the same error.

The following is the result when I try to compile with javaee.jar in my lib directory versus having javaee.jar in the glashfish\lib directory:

    C:\bee>copy c:\glassfish3\glassfish\lib\javaee.jar c:\bee\lib\javaee.jar  
    Overwrite c:\bee\lib\javaee.jar? (Yes/No/All): yes  
            1 file(s) copied.  
      
    C:\bee>javac -g -d .\build\classes -cp "C:\bee\lib\javaee.jar;C:\bee\lib\production\jr.jar;C:\bee\build\classes" -sourcepath "C:\bee\src\java" src\java\com\javaranch\drive\BeeServlet.java  
    src\java\com\javaranch\drive\BeeServlet.java:4: package javax.servlet.http does not exist  
    import javax.servlet.http.*;  
    ^  
    src\java\com\javaranch\drive\BeeServlet.java:6: cannot find symbol  
    symbol: class HttpServlet  
    public class BeeServlet extends HttpServlet  
                                    ^  
    src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol  
    symbol  : class HttpServletRequest  
    location: class com.javaranch.drive.BeeServlet  
        public void doGet( HttpServletRequest request, HttpServletResponse response )  
                           ^  
    src\java\com\javaranch\drive\BeeServlet.java:8: cannot find symbol  
    symbol  : class HttpServletResponse  
    location: class com.javaranch.drive.BeeServlet  
        public void doGet( HttpServletRequest request, HttpServletResponse response )  
                                                       ^  
    4 errors  
      
    C:\bee>javac -g -d .\build\classes -cp "C:\glassfish3\glassfish\lib\javaee.jar;C:\bee\lib\production\jr.jar;C:\bee\build\classes" -sourcepath "C:\bee\src\java" src\java\com\javaranch\drive\BeeServlet.java  
      
    C:\bee>  

[Jaikiran Pai]

Richard Broersma wrote:
Since the javaee.jar in my lib dir is a direct (and repeated refreshed) copy of the javaee.jar in the glassfish lib directory, I suspect there is another reason why the compilation is failing. Could it be the modern versions of javaee.jar rely on peer jar file in the glashfish lib directory?

Any thoughts?

I should have checked this before. I just looked at my glassfish installation and that specific jar and it turns out to be a MANIFEST only jar file. What this means is the javaee.jar doesn't have any classes within itself, but has a META-INF/MANIFEST.MF file which has a ClassPath attribute which points to (relative) locations of other jars containing the relevant classes. So if you copy that javaee.jar from the glassfish/lib to some of the place, you'll also have to copy the other jars referenced in the ClassPath attribute to appropriate locations so that the relative paths specified there can work. For example, the MANIFEST.MF of that jar contains:

Class-Path: ../modules/javax.servlet.jar ../modules/endorsed/javax.ann
 otation.jar ../modules/javax.ejb.jar ../modules/javax.transaction.jar
  ../modules/javax.enterprise.deploy.jar ../modules/javax.management.j
 2ee.jar ../modules/javax.resource.jar ../modules/javax.security.auth.
 message.jar ../modules/javax.security.jacc.jar ../modules/webservices
 -osgi.jar ../modules/jaxb-osgi.jar ../modules/endorsed/jaxb-api-osgi.
 jar ../modules/endorsed/webservices-api-osgi.jar ../modules/mail.jar 
 ../modules/jsf-api.jar ../modules/javax.servlet.jsp.jar ../modules/ja
 vax.servlet.jsp.jstl.jar ../modules/javax.persistence.jar ../modules/
 javax.jms.jar ../modules/bean-validator.jar ../modules/weld-osgi-bund
 le.jar ../../mq/lib/jaxm-api.jar

 

So wherever you copy that jar, you'll also need to create the "modules" folder at the right location and then copy over the other jars too.

The reason why this works if you just point to the glassfish/lib/javaee.jar (without moving it to some other folder) is because the relative paths of the referenced jars holds good.

[Richard Broersma]

Thanks! That fix it:

C:\bee\lib\development>xcopy /E c:\glassfish3\glassfish\modules .\modules\
C:\glassfish3\glassfish\modules\acc-config.jar
...
253 File(s) copied

C:\bee\lib\development>cd ..\..

C:\bee>javac -g -d .\build\classes -cp "C:\bee\lib\development\lib\javaee.jar;C:\bee\lib\production\jr.jar;C:\bee\build\classes" -sourcepath "C:\bee\src\java
 src\java\com\javaranch\drive\BeeServlet.java

C:\bee>

Now regarding the instruction in the Cattle Drive (i.e. Tree struction and files to be copied), should these instructions be amended considering the makeup of modern versions of glassfish?

[Carol Murphy]

I love a happy ending. Sigh.