[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
YunFeng Ma updated GERONIMODEVTOOLS-440:
----------------------------------------
Attachment: GERONIMODEVTOOLS-440.patch
We've had a method unmarshalFilterDeploymentPlan( IFile file ) in JAXBUtils
which use NamespaceFilter to convert the old deployment plan to the current
version. I think we should always use this method to unmarshal the deployment
plan, instead of method unmarshalDeploymentPlan(IFile file).
This patch removed method unmarshalDeploymentPlan(IFile file) and changed the
codes which invoke unmarshalDeploymentPlan(IFile file) to
unmarshalFilterDeploymentPlan( IFile file ).
> Convert the old deployment plan to the current version using NamespaceFilter
> ----------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-440
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-440
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 2.1.x
> Reporter: YunFeng Ma
> Assignee: Tim McConnell
> Attachments: GERONIMODEVTOOLS-440.patch
>
>
> GEP can not open the following old deployment plan:
> {noformat}
> <openejb-jar xmlns="http://www.openejb.org/xml/ns/openejb-jar-2.1"
> xmlns:nam="http://geronimo.apache.org/xml/ns/naming-1.2"
> xmlns:sec="http://geronimo.apache.org/xml/ns/security-1.2"
> xmlns:sys="http://geronimo.apache.org/xml/ns/deployment-1.2">
>
> <sys:environment>
> <sys:moduleId>
> <sys:groupId>samples</sys:groupId>
> <sys:artifactId>MDBDemo</sys:artifactId>
> <sys:version>2.1</sys:version>
> <sys:type>car</sys:type>
> </sys:moduleId>
> <sys:dependencies>
> <sys:dependency>
> <sys:groupId>org.apache.geronimo.configs</sys:groupId>
> <sys:artifactId>activemq-ra</sys:artifactId>
> <sys:type>car</sys:type>
> </sys:dependency>
> </sys:dependencies>
> <sys:hidden-classes/>
> <sys:non-overridable-classes/>
> </sys:environment>
>
> <enterprise-beans>
> <message-driven>
> <ejb-name>SampleMDB</ejb-name>
> <nam:resource-adapter>
> <nam:resource-link>ActiveMQ RA</nam:resource-link>
> </nam:resource-adapter>
> <activation-config>
> <activation-config-property>
>
> <activation-config-property-name>destination</activation-config-property-name>
>
> <activation-config-property-value>SendReceiveQueue</activation-config-property-value>
> </activation-config-property>
> <activation-config-property>
>
> <activation-config-property-name>destinationType</activation-config-property-name>
>
> <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
> </activation-config-property>
> </activation-config>
> <nam:ejb-ref>
> <nam:ref-name>CustomerHomeRemote</nam:ref-name>
> <nam:ejb-link>CustomerEJB</nam:ejb-link>
> </nam:ejb-ref>
> </message-driven>
>
> <entity>
> <ejb-name>CustomerEJB</ejb-name>
> <jndi-name>CustomerHomeRemote</jndi-name>
> <local-jndi-name/>
> <nam:resource-ref>
> <nam:ref-name>jdbc/ibm-demo</nam:ref-name>
> <nam:resource-link>SystemDatasource</nam:resource-link>
> </nam:resource-ref>
> </entity>
> </enterprise-beans>
> </openejb-jar>
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.