geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@geronimo.apache.org
Subject [jira] Updated: (GERONIMO-300) Deployer reports a wrong cause when a given module doesn't exist
Date Tue, 05 Oct 2004 18:00:32 GMT
The following issue has been updated:

    Updater: Dain Sundstrom (mailto:dsundstrom@gluecode.com)
       Date: Tue, 5 Oct 2004 11:00 AM
    Changes:
             Version changed from 1.0-M3
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/GERONIMO-300?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-300

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-300
    Summary: Deployer reports a wrong cause when a given module doesn't exist
       Type: Bug

     Status: Unassigned
   Priority: Trivial

    Project: Apache Geronimo
 Components: 
             deployment
   Versions:
             1.0-M2

   Assignee: 
   Reporter: Jacek Laskowski

    Created: Thu, 16 Sep 2004 1:50 PM
    Updated: Tue, 5 Oct 2004 11:00 AM

Description:
When Deployer is invoked with a module that doesn't exist it reports a wrong cause:

$ (cd target/geronimo-1.0-SNAPSHOT; java -jar bin/deployer.jar --module non/existing/module)
org.apache.geronimo.deployment.DeploymentException: No deployer found for this module type:
file:/c:/projects/geronimo/t
runk/modules/assembly/target/geronimo-1.0-SNAPSHOT/non/existing/module
        at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:168)
        at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(<generated>)
        at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:87)
        at org.apache.geronimo.gbean.jmx.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
        at org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
        at org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:765)
        at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:218)
        at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:121)
        at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:86)
        at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:121)
        at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:121)
        at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerIntercep
tor.java:205)
        at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1079)
        at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:231)
        at org.apache.geronimo.system.main.CommandLine.main(CommandLine.java:93)

It should validate if a given module exists at all before handing it over to module deployers.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message