RE: [M2]weblogic:appc classpath issue
I am glad that it is working now. I am anxious to push it up onto the snapshot server. Feel free to let me know what else I can add to help you out. You can enter JIRA tickets in the mojo section so I can track what you need. If you can clarify what you mean by autotypes I will look into that. I hope this weekend to add service gen and jwsc support. Also specify which version of Weblogic you are running. The code it different for 9.0 and 8.1 so that helps me know where to start. Keep the bug reports and feature requests coming and I will work on them as I have time. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 8:55 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue I downloaded the code from codehaus SNV and it working fine now. Thanks again! Any plans to include autotypes and servicegen goals in the plugin? :) Currently i'm using maven-antrun-plugin to use weblogic servicegen task. Scott Ryan-2 wrote: I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480
RE: [M2]weblogic:appc classpath issue
By autotpes i meant the weblogic.ant.taskdefs.webservices.javaschema.JavaSchema task to generate xml based on Java types. I'm using wls 8.1 sp4. Scott Ryan-2 wrote: I am glad that it is working now. I am anxious to push it up onto the snapshot server. Feel free to let me know what else I can add to help you out. You can enter JIRA tickets in the mojo section so I can track what you need. If you can clarify what you mean by autotypes I will look into that. I hope this weekend to add service gen and jwsc support. Also specify which version of Weblogic you are running. The code it different for 9.0 and 8.1 so that helps me know where to start. Keep the bug reports and feature requests coming and I will work on them as I have time. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 8:55 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue I downloaded the code from codehaus SNV and it working fine now. Thanks again! Any plans to include autotypes and servicegen goals in the plugin? :) Currently i'm using maven-antrun-plugin to use weblogic servicegen task. Scott Ryan-2 wrote: I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java
Re: [M2]weblogic:appc classpath issue
Can you also tell to WHICH maven repository you will publish it ? Thank you very much for your efforts. 2006/11/2, Dmystery [EMAIL PROTECTED]: Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle- server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java :155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030
RE: [M2]weblogic:appc classpath issue
I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20
RE: [M2]weblogic:appc classpath issue
The 2.8.0 version of the plugin is for 8.1.4 and above. It will work for 8.1.3 and below for all but remote deployments. If you need it I can retro fit the remote deployment back to 8.1.3 2.8.0-SNAPSHOT supports the 8.1 version of Weblogic for all versions except remote deployment which requires sp4 and above 2.9.0-SNAPSHOT supports 9.0 with all patch levels The 2.9.0 code is on the trunk and the 2.8.0 code is on the branch. Let me know if you need more information. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Jonas Olsson [mailto:[EMAIL PROTECTED] Sent: Thursday, November 02, 2006 2:41 AM To: Maven Users List Subject: SV: [M2]weblogic:appc classpath issue Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out on this fix? /jonas -Ursprungligt meddelande- Från: Manu [mailto:[EMAIL PROTECTED] Skickat: den 2 november 2006 10:27 Till: Maven Users List Ämne: Re: [M2]weblogic:appc classpath issue Can you also tell to WHICH maven repository you will publish it ? Thank you very much for your efforts. 2006/11/2, Dmystery [EMAIL PROTECTED]: Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle- server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192
RE: [M2]weblogic:appc classpath issue
I downloaded the code from codehaus SNV and it working fine now. Thanks again! Any plans to include autotypes and servicegen goals in the plugin? :) Currently i'm using maven-antrun-plugin to use weblogic servicegen task. Scott Ryan-2 wrote: I would love to push it but I only have access to SVN at codehaus. I do not have the authority to push up a snapshot any longer and the people who can don't seem to have access to the Weblogic jars required to build the code. I hope I can get this worked out this week. Until then you can just download the code from SVN and run mvn install to place it in your local repository to test. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 9:06 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20
RE: [M2]weblogic:appc classpath issue
I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534
RE: [M2]weblogic:appc classpath issue
The fix is in the code on the branch 2.8.0. i am trying to publish the fixes if I can get authorization. You can pull down the code and build it and that should fix your classpath issues. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273
RE: [M2]weblogic:appc classpath issue
The code is checked in to SVN to fix this. I will try to push a new snapshot as soon as i can get authorization Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Dmystery [mailto:[EMAIL PROTECTED] Sent: Monday, October 30, 2006 11:47 PM To: users@maven.apache.org Subject: RE: [M2]weblogic:appc classpath issue Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke
RE: [M2]weblogic:appc classpath issue
Thanks Scott. It would be great if you can push the latest snapshot to the repository now. Scott Ryan-2 wrote: I have refactored the 2.8.0 plugin to fix that problem. I have changed some of the parameters and since the website can only support one version of the plugin I need to add a page to describe the new settings for the 2.8.0 plugin. I will be pushing the latest snapshot up to the repository once I have completed that documentation. This fixes the classpath issue both in appc and the client gen mojos. I have not updated the 2.9.0 version as the 9.2 release broke all the apis I was using so i need to refactor to use the new API's. Let me know if you would prefer I push up the 2.8.0 version now and just post the changes on a note to the user list. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Manu [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 31, 2006 12:07 PM To: Maven Users List Subject: Re: [M2]weblogic:appc classpath issue Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412
Re: [M2]weblogic:appc classpath issue
Hi, I have the same problem. I need to explicitly set the entire classpath by hand to have it worked. In other words, I'm defining another time all the dependencies that already are in the pom. The plugin does not seem to take into account the dependencies. By the way, i'm using version 2.8.0-SNAPSHOT Thxs Manu 2006/10/31, Dmystery [EMAIL PROTECTED]: Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java :387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at
RE: [M2]weblogic:appc classpath issue
I still have issue in compiling the ejb jar file. It simply fails to find all
the dependencies in the classpath.
Here is the plugin definition again.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.version}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
All the required jars for appc are defined as 'compile' dependecies in the
pom. Still it gives me a NoClassDefFoundError for the required class files.
Scott Ryan-2 wrote:
How did you make out with the appc mojo? I am updating the plugin to
simplify it this weekend and will update the code with some code that was
posted in JIRA. Let me know your status and I will send out a note on the
weekend when the new code is available.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException
:
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it
is
optional), it fails to find some of the classes that it needs to compile
the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090s177.html#a7088731
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
Alos, looking at AppcMojo.class file, i dont see any default classpath being set. Here is the stack trace when i try to run the plugin. [INFO] Detailed Appc settings information AppcMojo[basicClientJar = false classpath = null compiler = null debugging = true deprecation = false forceGeneration = false idl = false idlDirectory = null idlFactrories = false idlMethodSignatures = null idlNoAbstractInterfaces = true idlNoValueTypes = true idlOrbix = false idlOverwrite = false idlVerbose = false idlVisiBroker = false iiop = false iiopDirectory = null javaOptions = null keepGenerated = true lineNumbers = true nowarnings = false objectPath = D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb- 1.0.jar optimization = false outputFile = null verbose = true version = false] [INFO] Argument List for Appc settings [-lineNumbers, -keepgenerated, -g, -verb ose, D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-1.0.jar] [appc] Created working directory: C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen [J2EE:160119]Appc is unable to process the file 'D:\Castle-maven\castle\server\s erver-ejb\target\castle-server-ejb-1.0.jar'. The following error occurred: java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB This is a compile dependency in the POM at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:502) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12 3) at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic ClassLoader.java:480) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass Loader.java:182) at java.lang.ClassLoader.loadClass(ClassLoader.java:299) at java.lang.ClassLoader.loadClass(ClassLoader.java:292) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass Loader.java:224) at weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343) at weblogic.ejb20.deployer.BeanInfoImpl.init(BeanInfoImpl.java:192) at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.init(ClientDrivenB eanInfoImpl.java:179) at weblogic.ejb20.deployer.SessionBeanInfoImpl.init(SessionBeanInfoImp l.java:74) at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl. java:367) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M BeanDeploymentInfoImpl.java:548) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.init(MBeanDeploymen tInfoImpl.java:232) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387) at weblogic.appc.compileEJB(appc.java:802) at weblogic.appc.compileEJB(appc.java:776) at weblogic.appc.compileInput(appc.java:463) at weblogic.appc.runBody(appc.java:184) at weblogic.utils.compiler.Tool.run(Tool.java:192) at weblogic.utils.compiler.Tool.run(Tool.java:147) at weblogic.appc.main(appc.java:1030) at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:276) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi fecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Dmystery wrote: I
RE: [M2]weblogic:appc classpath issue
That is what i thought. I should not a classpath. Most of my dependencies
are with compile scope and yes i have an ejb jar file that i'm trying to
compile. i cannot send u the exact snippet as i'm on a vacation :). Will get
in touch next week.
thanks.
Scott Ryan-2 wrote:
You should not need a classpath as that is included for the clientgen part
of the plugin. The mojo should recognize the proper classpath from the
plugin dependencies. Are all your dependencies set to the default scope
or
are some set to some other scope like provided etc? Let me try the latest
plugin against my test suite tonight and give you some more feedback.
Just
to clarify you have an ejb jar file you are trying to appc? I have had
success with that. if you could send me a snippet of the issues you see
when you try with out the classpath that would help a lot. i will try to
get you an answer back this evening unless someone else on the list has an
answer before that.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException
:
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it
is
optional), it fails to find some of the classes that it needs to compile
the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a6929932
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
How did you make out with the appc mojo? I am updating the plugin to
simplify it this weekend and will update the code with some code that was
posted in JIRA. Let me know your status and I will send out a note on the
weekend when the new code is available.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException :
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it is
optional), it fails to find some of the classes that it needs to compile the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [M2]weblogic:appc classpath issue
You should not need a classpath as that is included for the clientgen part
of the plugin. The mojo should recognize the proper classpath from the
plugin dependencies. Are all your dependencies set to the default scope or
are some set to some other scope like provided etc? Let me try the latest
plugin against my test suite tonight and give you some more feedback. Just
to clarify you have an ejb jar file you are trying to appc? I have had
success with that. if you could send me a snippet of the issues you see
when you try with out the classpath that would help a lot. i will try to
get you an answer back this evening unless someone else on the list has an
answer before that.
Scott Ryan
Chief Technology Officer
Soaring Eagle L.L.C.
[EMAIL PROTECTED]
www.soaringeagleco.com
(303) 263-3044
-Original Message-
From: Dmystery [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 18, 2006 2:39 AM
To: users@maven.apache.org
Subject: [M2]weblogic:appc classpath issue
I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin
definition.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.8.0-SNAPSHOT/version
configuration
objectPath${project.build.directory}/${project.artifactId}-${project.versi
on}.jar/objectPath
verbosetrue/verbose
debuggingtrue/debugging
nowarningsfalse/nowarnings
lineNumberstrue/lineNumbers
keepGeneratedtrue/keepGenerated
classpath${project.runtimeClasspathElements}/classpath
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
/plugin
The ${project.runtimeClasspathElements} is a string like [somedir\jar1,
somedir\jar2]. Because of this the plugin throws a
org.codehaus.plexus.component.configurator.ComponentConfigurationException :
Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]'
Are we supposed to provide classpath/classpath in the first place? or
will it consider ${project.runtimeClasspathElements} as the default
classpath? (I guess not).
If i remove the classpath/classpath from the plugin definition (as it is
optional), it fails to find some of the classes that it needs to compile the
ejb.jar even though they are defined as dependencies in the project.
Let me know if i'm doing something wrong.
--
View this message in context:
http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68
71847
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
