Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <1925961616.1139431860542.JavaMail.jira@ajax.apache.org>
Date: Wed, 8 Feb 2006 21:51:00 +0100 (CET)
From: "Sachin Patel (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Resolved: (GERONIMODEVTOOLS-64) Tolerate projects or EARs
 without Geronimo facet.
In-Reply-To: <1751505829.1139428627384.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-64?page=all ]
     
Sachin Patel resolved GERONIMODEVTOOLS-64:
------------------------------------------

    Resolution: Won't Fix

The facet will need to be created programatically.  J2EE tooling is not making the dd's id's unique between projects.  So if the geronimo facet is not created, then the Geronimo runtime uses the dd id's as its configID which will cause conflicts when deploying multiple projects that do not contain a geronimo specific deployment plan.

> Tolerate projects or EARs without Geronimo facet.
> -------------------------------------------------
>
>          Key: GERONIMODEVTOOLS-64
>          URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-64
>      Project: Geronimo-Devtools
>         Type: Bug
>  Environment: Windows XP
>     Reporter: Kathy Chan

>
> Driver:  WTP M101 0207 and 0206 Geronimo plugins.
> If I add more then one EAR targetted to Geronimo runtime but do not add the Geronimo facet, then I get the error:
> !MESSAGE Configuration with id Application_IDalready exists.  Existing configuration will be overwri
> tten with redeploy.
> Deployer operation failed: Could not parse application.xml
> org.apache.geronimo.common.DeploymentException: Could not parse application.xml
>         at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getEarPlan(EARConfigBuilder.java:176
> )
>         at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.getDeploymentPlan(EARConfigBuilder.j
> ava:122)
>         at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(<
> generated>)
>         at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
>         at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
>         at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118)
>         at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800)
>         at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
>         at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36)
>         at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.
> java:96)
>         at org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$6abab4ad.getDeploym
> entPlan(<generated>)
>         at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:219)
> Doing the same with Web project works beacuse the configID is falling back on the context root which will be uniquiq for all web projects in the workbench.
> I think the same defaulting should happen for EAR and other J2EE projects (other than Web project) so that adding the Geronimo facet is not "required" but just "nice to have".  This is especially important for code that programmatically create projects and EARs so that they are not "required" to add the default facet.

-- 
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