geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim McConnell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMODEVTOOLS-190) Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0, deployment-1.2 etc)
Date Wed, 10 Oct 2007 03:00:50 GMT

    [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533577
] 

Tim McConnell commented on GERONIMODEVTOOLS-190:
------------------------------------------------

Hi again Miroslav, the limitations of the 2.0 version of the Eclipse plugin are related only
to editing some of the 2.0 deployment plans using the Eclipse editors, which will in fact
be fixed in the next maintenace release. There are no limitations that I'm aware of that would
prevent you from deploying any EJB EAR application to the Geronimo 2.0.1 server. In fact,
many EJB EAR applications have successfully be deployed using the plugin. If you have one
that is not working correctly though, would it be possible for you to attach it to this JIRA
(or a functioning facsimile if you cannot provide the actual EAr) so that we can investigate
?? If so, that would be extremely helpful. Thanks much

> Error opening v2.0 of Geronimo plans (which point to web-2.0, naming-1.2, security-2.0,
deployment-1.2 etc)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-190
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-190
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.0.0
>            Reporter: Shiva Kumar H R
>            Assignee: Tim McConnell
>             Fix For: 2.0.2
>
>         Attachments: HelloWorld.war
>
>
> Import the attached HelloWorld.war and double click on geronimo-web.xml. An error window
will pop up saying " .. elements in the plan may not be qualified ..."
> This is caused by trying to parse v2.0 of Geronimo plans with v1.1 of  schemas.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message