[ http://issues.apache.org/jira/browse/GERONIMO-2583?page=all ]
David Jencks closed GERONIMO-2583.
----------------------------------
Resolution: Fixed
Moving the geronimo-deploy-tool dependency from geronimo-gbean-deployer to
hot-deployer seems to eliminate this problem and I believe the console, online,
offline, hot, and jsr-88 (e.g through the tck) deployment methods all still
work.
Rakesh, in this case assuming that existing apparently working configs had the
correct classpath was wrong :-(
A lot of dependency/classloader problems are caused IMO by two things:
- geronimo dependency tree different from maven dependency tree. We could fix
a lot of these problems by building the configs with the module jars that they
use: then other module jars could depend on configs, like they will in
geronimo, instead of the jar dependencies of the configs.
- a lot of module jars and configs have a lot of unneeded dependencies. If we
could find a way to automatically check some of these we might be able to slim
the poms and the problems down considerably.
trunk rev. 483226
branches/1.2 rev 483231
> java.lang.NoClassDefFoundError:
> org/apache/geronimo/deployment/plugin/ConfigIDExtractor
> ---------------------------------------------------------------------------------------
>
> Key: GERONIMO-2583
> URL: http://issues.apache.org/jira/browse/GERONIMO-2583
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Hot Deploy Dir
> Affects Versions: 1.2
> Environment: Windows Xp, should be valid for all platforms
> Reporter: Rakesh Midha
> Assigned To: David Jencks
> Priority: Blocker
> Fix For: 1.2
>
> Attachments: dependencyonlyjsr88.patch, hotdeploygbean.patch
>
>
> Hello
> This issue was discussed before in
> http://www.mail-archive.com/[email protected]/msg28048.html and I think
> the patch was provided as a part of M2 migration in
> http://issues.apache.org/jira/browse/GERONIMO-2067#action_12423814 (It says
> any other issue open new JIRA, so opening this one)
> I downloaded latest trunk, and tried to use hot-deployer. Every time I try to
> use hot-deployer I get exception.
> java.lang.NoClassDefFoundError:
> org/apache/geronimo/deployment/plugin/ConfigIDExtractor
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
> 3)
> at
> org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(
> JarFileClassLoader.java:52)
> at
> org.apache.geronimo.kernel.classloader.JarFileClassLoader$6.run(JarFi
> leClassLoader.java:298)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(J
> arFileClassLoader.java:250)
> at
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
> ltiParentClassLoader.java:292)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
> ltiParentClassLoader.java:276)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at
> org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
> ltiParentClassLoader.java:276)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:141)
> at
> org.apache.geronimo.deployment.hot.DirectoryMonitor.class$(DirectoryM
> onitor.java:47)
> at
> org.apache.geronimo.deployment.hot.DirectoryMonitor.calculateModuleId
> (DirectoryMonitor.java:369)
> at
> org.apache.geronimo.deployment.hot.DirectoryMonitor.initialize(Direct
> oryMonitor.java:238)
> at
> org.apache.geronimo.deployment.hot.DirectoryMonitor.run(DirectoryMoni
> tor.java:214)
> at java.lang.Thread.run(Thread.java:534)
> The class is in geronimo-deploy-jsr88, and hot-deploy pom.xml already shows
> hot-deploy to be dependent on geronimo-deploy-jsr88, which means the above
> class should be available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
