[
https://issues.apache.org/jira/browse/GERONIMO-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797010#action_12797010
]
Ivan commented on GERONIMO-5012:
--------------------------------
Hi, Łukasz
It is a bug in Geronimo, and I think it should exist for a long time.
However, you could add a empty ejb-jar.xml file in the META-INF folder to
workaround it. The reason is that Geronimo finds the module ID according to the
standard Java EE deployment file it finds. e.g. Once it found a ejb-jar.xml in
the META-INF folder, it would check the openejb-jar.xml file. But in EJB 3.0,
ejb-jar.xml is not a must file.
Thanks for pointing it out !
Ivan
> "Redeploy application" in Web console does not work (G2.2)
> ----------------------------------------------------------
>
> Key: GERONIMO-5012
> URL: https://issues.apache.org/jira/browse/GERONIMO-5012
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Environment: G 2.2 with Tomcat 6, Windows XP, Java 6
> Reporter: Łukasz Budnik
> Priority: Minor
>
> When using http://localhost/console/portal/Applications/Deploy%20New to
> redeploy the application I keep getting the following message:
> Unable to identify modules to replace. Check if it has already been stopped
> or undeployed.
> null
> (no exceptions logged in geronimo.out)
> I have to uninstall the application using
> http://localhost/console/portal/Applications/Web%20App%20WARs or
> http://localhost/console/portal/Applications/EJB%20JARs and then deploy it
> from the scratch.
> not a blocker, but quite annoying.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
