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

Shiva Kumar H R commented on GERONIMODEVTOOLS-190:
--------------------------------------------------

We are re-looking at some of the basics of Geronimo Eclipse Plug-in's Editors 
for Geronimo deployment plans: 
http://www.mail-archive.com/dev@geronimo.apache.org/msg51801.html

One promising approach seems to be to use JSR-88 DConfigBeans as the model 
framework for Geronimo deployment plan editors.

However, Geronimo doesn't yet have a complete set of JSR-88 DConfigBeans. The 
work I am currently doing on Geronimo JIRAs 3254, 3433 & 3432 (Admin Console 
Wizards to auto generate Geronimo Deployment Plans) will find/add many of the 
missing DConfigBeans. Once that is complete I am planning to take up this JIRA.

Meanwhile, any and all help is welcome.

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

Reply via email to