Hi,

I have a question on how to use the <wlclasspath/> nested element to
turn off warnings that occur when the home and remote interfaces of a
bean are on the system classpath used to run weblogic.ejbc. The User
Manual suggests that the standard weblogic classes should be set with
the wlclasspath attribute (or equivalent nested element) and the home
and remote interfaces located with the standard classpath attribute.
However, as soon as I point wlclasspath to weblogic.jar (which I assume
is what it's after), my <ejbjar> task can no longer resolve some of the
"helper" classes. If I run ant with the -debug flag, I see the
following:

     [ejbc] Forking C:\jdk1.3.1_01\jre\..\bin\java.exe -classpath
C:\bea\wlserve
r6.0\lib\weblogic.jar weblogic.ejbc20
C:\Latest\Starman\Build\jars\Reporting-gen
eric.jar C:\Latest\Starman\Build\jars\Reporting.jar
Execute:Java13CommandLauncher: C:\jdk1.3.1_01\jre\..\bin\java.exe
-classpath C:\
bea\wlserver6.0\lib\weblogic.jar weblogic.ejbc20
C:\Latest\Starman\Build\jars\Re
porting-generic.jar C:\Latest\Starman\Build\jars\Reporting.jar
     [ejbc] java.lang.NoClassDefFoundError:
com/stargus/platform/framework/repor
t/manager/AsyncReportRunListener
     [ejbc]     at java.lang.ClassLoader.defineClass0(Native Method)
     [ejbc]     at
java.lang.ClassLoader.defineClass(ClassLoader.java:486)
     [ejbc]     at
java.security.SecureClassLoader.defineClass(SecureClassLoader
.java:111)
     [ejbc]     at
weblogic.utils.classloaders.GenericClassLoader.findLocalClass
(GenericClassLoader.java:304)
     [ejbc]     at
weblogic.utils.classloaders.GenericClassLoader.findClass(Gene
ricClassLoader.java:155)
     [ejbc]     at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
     [ejbc]     at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
     [ejbc]     at
weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.j
ava:194)
     [ejbc]     at
weblogic.ejb20.deployer.BeanInfoImpl.<init>(BeanInfoImpl.java
:116)
     [ejbc]     at
weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(Clien
tDrivenBeanInfoImpl.java:116)
     [ejbc]     at
weblogic.ejb20.deployer.SessionBeanInfoImpl.<init>(SessionBea
nInfoImpl.java:47)
     [ejbc]     at
weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanI
nfoImpl.java:206)
     [ejbc]     at
weblogic.ejb20.deployer.DeploymentInfoImpl.initializeBeanInfo
s(DeploymentInfoImpl.java:157)
     [ejbc]     at
weblogic.ejb20.deployer.DeploymentInfoImpl.<init>(DeploymentI
nfoImpl.java:86)
     [ejbc]     at
weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:107
)
     [ejbc]     at weblogic.ejbc20.runBody(ejbc20.java:703)
     [ejbc]     at weblogic.utils.compiler.Tool.run(Tool.java:81)
     [ejbc]     at weblogic.ejbc20.main(ejbc20.java:849)
     [ejbc] Exception in thread "main"

BUILD FAILED

C:\Latest\Starman\Build\build.xml:476: Exception while calling
weblogic.ejbc20.
Details: Ejbc reported an error
        at
org.apache.tools.ant.taskdefs.optional.ejb.WeblogicDeploymentTool.bui
ldWeblogicJar(WeblogicDeploymentTool.java:464)
        at
org.apache.tools.ant.taskdefs.optional.ejb.WeblogicDeploymentTool.wri
teJar(WeblogicDeploymentTool.java:481)
        at
org.apache.tools.ant.taskdefs.optional.ejb.GenericDeploymentTool.proc
essDescriptor(GenericDeploymentTool.java:358)
        at
org.apache.tools.ant.taskdefs.optional.ejb.EjbJar.execute(EjbJar.java
:525)
        at org.apache.tools.ant.Task.perform(Task.java:217)
        at org.apache.tools.ant.Target.execute(Target.java:184)
        at org.apache.tools.ant.Target.performTasks(Target.java:202)
        at org.apache.tools.ant.Project.executeTarget(Project.java:601)
        at org.apache.tools.ant.Project.executeTargets(Project.java:560)
        at org.apache.tools.ant.Main.runBuild(Main.java:454)
        at org.apache.tools.ant.Main.start(Main.java:153)
        at org.apache.tools.ant.Main.main(Main.java:176)
--- Nested Exception ---
Ejbc reported an error
        at
org.apache.tools.ant.taskdefs.optional.ejb.WeblogicDeploymentTool.bui
ldWeblogicJar(WeblogicDeploymentTool.java:458)
        at
org.apache.tools.ant.taskdefs.optional.ejb.WeblogicDeploymentTool.wri
teJar(WeblogicDeploymentTool.java:481)
        at
org.apache.tools.ant.taskdefs.optional.ejb.GenericDeploymentTool.proc
essDescriptor(GenericDeploymentTool.java:358)
        at
org.apache.tools.ant.taskdefs.optional.ejb.EjbJar.execute(EjbJar.java
:525)
        at org.apache.tools.ant.Task.perform(Task.java:217)
        at org.apache.tools.ant.Target.execute(Target.java:184)
        at org.apache.tools.ant.Target.performTasks(Target.java:202)
        at org.apache.tools.ant.Project.executeTarget(Project.java:601)
        at org.apache.tools.ant.Project.executeTargets(Project.java:560)
        at org.apache.tools.ant.Main.runBuild(Main.java:454)
        at org.apache.tools.ant.Main.start(Main.java:153)
        at org.apache.tools.ant.Main.main(Main.java:176)

Obviously it has something to do with the forking jvm, but I'm darned if
I can figure it out. Any thoughts?

Cheers,

Matt

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to