[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019253#comment-13019253 ]
Han Hong Fang commented on GERONIMODEVTOOLS-728:
------------------------------------------------
http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0 is the excepted namespace for ejb, but in the sample attached, http://openejb.apache.org/xml/ns/openejb-jar-2.2 is used instead of http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0. During EAR file import, the deployment plan will be unmarshalled and then marchalled to filter the deployment plan. Elements lost during this conversion because incorrect namespace is used for ejb elements. To correct the EAR, please replace prefix ejb with prefix ns5, which is also defined in the sample. (BTW, I think ns5 should be replace with a meaningful prefix in GEP code)
> The original geronimo deployment plan will be cleaned when importing an existing EAR project
> --------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-728
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-728
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 3.0
> Environment: helios jee sr1
> Reporter: Forrest Xia
> Attachments: corbahellobean_ejb_ear.ear
>
>
> When importing an existing EAR into eclipse, if selecting geronimo server as the target runtime, the original geronimo deployment descriptor will be flushed.
> For example, the plan in the ear file is like this:
>
>
> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
> xmlns:bp="http://www.osgi.org/xmlns/blueprint/v1.0.0"
> xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"
> xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2" xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
> xmlns:jaspi="http://geronimo.apache.org/xml/ns/geronimo-jaspi"
> xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0"
> xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2" xmlns:ns5="http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0"
> xmlns:pers="http://java.sun.com/xml/ns/persistence" xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0" xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
>
>
> default
> corbahellobean_ejb
> 1.0
> car
>
>
>
>
> HelloEJBRemote
> HelloEJBRemote
> IOR3
>
>
>
> After import, the deployment descriptor will be flushed like this:
>
> xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
> xmlns:bp="http://www.osgi.org/xmlns/blueprint/v1.0.0"
> xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"
> xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
> xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2" xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
> xmlns:jaspi="http://geronimo.apache.org/xml/ns/geronimo-jaspi"
> xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0"
> xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2" xmlns:ns5="http://geronimo.apache.org/xml/ns/j2ee/ejb/openejb-2.0"
> xmlns:pers="http://java.sun.com/xml/ns/persistence" xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0" xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
>
>
> default
> corbahellobean_ejb
> 1.0
> car
>
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira