Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 60483 invoked from network); 16 Sep 2004 20:50:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Sep 2004 20:50:10 -0000 Received: (qmail 85629 invoked by uid 500); 16 Sep 2004 20:49:57 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 85490 invoked by uid 500); 16 Sep 2004 20:49:56 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 85472 invoked by uid 99); 16 Sep 2004 20:49:56 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 16 Sep 2004 13:49:53 -0700 Received: (qmail 14901 invoked from network); 16 Sep 2004 20:51:40 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 16 Sep 2004 20:51:40 -0000 Message-ID: <139565816.1095367900412.JavaMail.apache@nagoya> Date: Thu, 16 Sep 2004 13:51:40 -0700 (PDT) From: dev@geronimo.apache.org To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-300) Deployer reports a wrong cause when a given module doesn't exist Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Message: A new issue has been created in JIRA. --------------------------------------------------------------------- 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 1.0-M3 Assignee: Reporter: Jacek Laskowski Created: Thu, 16 Sep 2004 1:50 PM Updated: Thu, 16 Sep 2004 1:50 PM 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() 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