geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Midha (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2583) java.lang.NoClassDefFoundError: org/apache/geronimo/deployment/plugin/ConfigIDExtractor
Date Thu, 30 Nov 2006 07:25:21 GMT
    [ ] 
Rakesh Midha commented on GERONIMO-2583:

David, I think I agree with your point. You are right, it is not acceptable to include hot
deployer classes in any other configuration. My mistake I didn't think it from that angle.

Actually I added dependency on geronimo-hot-deploy and geronimo-system in config/geronimo-gbean-deployer
just to make classloader hierarchy cleaner. It is not essential for geronimo-gbean-deployer
to be dependent on geronimo-hot-deploy and geronimo-system.

Only dependency required to get hot-deployer working is dependency of config/geronimo-gbean-deployer
 on geronimo-deploy-jsr88. I think that is acceptable. Right?

So summarising this : 
There are two ways to solve this problem:
1. Add only 
+        <dependency>
+            <groupId>org.apache.geronimo.modules</groupId>
+            <artifactId>geronimo-deploy-jsr88</artifactId>
+            <version>${version}</version>
+        </dependency>
in config\geronimo-gbean-deployer

2. Move ConfigIdExtractor to geronimo-deploy-config, but this will require additional dependency
of geronimo-deploy-config on geronimo-system, geronimo-deployment and geronimo-j2ee-deployment_1.1_spec

I still believe Method 1 is a clean way to get this done. I think it is essential that it
is finalized and committed as soon as possible because I think it is a blocker on hot-deployment

Please let me know what you think of it. I am doing a complete build and test run to make
sure that Method 1 doesn't fail anything. Will post a patch with changes required for method
1 or Method 2 which ever we decide to go with.

> java.lang.NoClassDefFoundError: org/apache/geronimo/deployment/plugin/ConfigIDExtractor
> ---------------------------------------------------------------------------------------
>                 Key: GERONIMO-2583
>                 URL:
>             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
>             Fix For: 1.2
>         Attachments: hotdeploygbean.patch
> Hello
> This issue was discussed before in
and I think the patch was provided as a part of M2 migration in
(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(
>         at
> 3)
>         at org.apache.geronimo.kernel.classloader.JarFileClassLoader.access$200(
>         at org.apache.geronimo.kernel.classloader.JarFileClassLoader$
>         at Method)
>         at org.apache.geronimo.kernel.classloader.JarFileClassLoader.findClass(J
>         at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
>         at java.lang.ClassLoader.loadClass(
>         at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
>         at java.lang.ClassLoader.loadClass(
>         at org.apache.geronimo.kernel.config.MultiParentClassLoader.loadClass(Mu
>         at java.lang.ClassLoader.loadClass(
>         at java.lang.ClassLoader.loadClassInternal(
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(
>         at$(DirectoryM
>         at
> (
>         at
>         at
>         at
> 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:
For more information on JIRA, see:


View raw message