Conor,
I have upgraded to the new Beta 2 jar and made some minor changes to my
build.xml file to support your new ejbjar options. I love what you changed,
it works so much better.
I was having some problems that I hoped would be fixed, but are not. This is
leading me to believe it may be an environment setting. Here is my
environment:
1. Windows 2000
2. JDK 1.3.0
3. Ant 1.3 Beta 2
4. WebLogic 5.1
My session beans work great, but I get the following problem when trying to
process a CMP bean:
project-compile-ejbs:
[ejbjar] building AuthenticationDAO.jar with 5 files
[ejbc] [EJB]: Creating output
jar:D:\Projects\GuardianAngel\Development\lib\ejbs\AuthenticationDAO.jar
[ejbjar] Could not load class
com.bmc.guardianangel.dataaccess.user.UserAccount
for super class check
[ejbjar] Could not load class
com.bmc.guardianangel.dataaccess.user.UserAccountPK
for super class check
[ejbjar] Could not load class
com.bmc.guardianangel.dataaccess.user.UserAccountHome
for super class check
[ejbjar] Could not load class
com.bmc.guardianangel.dataaccess.user.UserAccountBean
for super class check
[ejbjar] building UserAccount.jar with 7 files
BUILD FAILED
D:\Projects\GuardianAngel\Development\build.xml:146: IOException while
adding entry
com\bmc\guardianangel\dataaccess\user\UserAccount
.class to jarfile from D:\Projects\GuardianAngel\Development\classes\
com\bmc\guardianangel\dataaccess\user\UserAccount
.class.D:\Projects\GuardianAngel\Development\classes\
com\bmc\guardianangel\dataaccess\user\UserAccount
.class (The filename, directory name, or volume label syntax is
incorrect)
--- Nested Exception ---
java.io.FileNotFoundException:
D:\Projects\GuardianAngel\Development\classes\
com\bmc\guardianangel\dataaccess\user\UserAccount
.class (The filename, directory name, or volume label syntax is
incorrect)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:64)
at java.io.FileInputStream.<init>(FileInputStream.java:95)
at
org.apache.tools.ant.taskdefs.optional.ejb.GenericDeploymentTool.addFileToJa
r(GenericDeploymentTool.java:237)
at
org.apache.tools.ant.taskdefs.optional.ejb.GenericDeploymentTool.writeJar(Ge
nericDeploymentTool.java:479)
at
org.apache.tools.ant.taskdefs.optional.ejb.WeblogicDeploymentTool.writeJar(W
eblogicDeploymentTool.java:411)
at
org.apache.tools.ant.taskdefs.optional.ejb.GenericDeploymentTool.processDesc
riptor(GenericDeploymentTool.java:383)
at
org.apache.tools.ant.taskdefs.optional.ejb.EjbJar.execute(EjbJar.java:413)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
Here is my current build.xml target for ejbjar:
<target name="project-compile-ejbs" depends="project-compile">
<ejbjar srcdir="${project.bin.dir}"
descriptordir="${project.src.dir}"
flatdestdir="yes"
classpath="${project.classpath};${project.bin.dir}">
<weblogic destdir="${project.deploymentjars.dir}"
/>
<include name="**/*ejb-jar.xml"/>
<exclude name="**/*weblogic*.xml"/>
</ejbjar>
</target>
My Ant variables:
project.bin.dir = <projectroot>/classes
project.src.dir = <projectroot>/src
project.deploymentjars.dir = <projectroot>/lib/ejbs
Apparently, it seems to be having problems loading the classes to build the
generic jar. The UserAccountBean extends a superclass that is in our
codebase. What may I have to change in the ejbjar configuration to get it to
see the superclass? My classpath at the time of Ant launch does NOT contain
the /classes directory, but the classpath passed into ejbjar does. What is
the tag doing during the superclass check and how could that fail if the
superclass is from a project superclass (that extends the typical EJB
superclass) rather than the typical EJB superclass.
Any help would be appreciated.
James
-----Original Message-----
From: Conor MacNeill [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 15, 2001 7:06 AM
To: [EMAIL PROTECTED]
Subject: ejbjar in Ant 1.3
I have just sent the Ant 1.3 Beta 2 announcement and I would just like to
draw the attention of the <ejbjar> users to the updated documentation. I
would appreciate feedback on these updates.
In particular, I would like to have any feedback from people using Weblogic
6.0 about whether they encounter any problems using <ejbjar> and <wlrun>. I
know a couple of users reported problems in the last couple of weeks and
I'd like to know if these problems remain.
Thanks
Conor