You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ivan (Commented) (JIRA)" <ji...@apache.org> on 2012/01/16 06:19:40 UTC

[jira] [Commented] (GERONIMO-6260) Could not redeploy EJB module

    [ https://issues.apache.org/jira/browse/GERONIMO-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13186702#comment-13186702 ] 

Ivan commented on GERONIMO-6260:
--------------------------------

Think that we need to consider more for the changes, the original logic is that it firstly checks spec deployment plan file to determine the application type, then read the corresponding Geronimo specific file, the real problem here is that, with the new specification, those plans are not must. The similar problem could be found with war. ear, car and etc, not only EJB. One possible solution may be, keep the current logic there, and if no catch, try to read those Geronimo plans.
                
> Could not redeploy EJB module
> -----------------------------
>
>                 Key: GERONIMO-6260
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6260
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 3.0-beta-1
>         Environment: win7 64bit, oracle jdk1.6.0_25
>            Reporter: Yi Xiao
>            Assignee: Yi Xiao
>              Labels: ejb, redeploy
>         Attachments: couldNotRedployEJB_6260.patch
>
>
> ERROR [DeploymentPortlet] Unable to identify modules to replace. Check if it has already been stopped or undeployed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira