[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079890#comment-13079890
]
Yi Xiao commented on GERONIMODEVTOOLS-759:
------------------------------------------
The newest path is OSGIBundleDeploy_759_persistence.patch.
I reconstruct the code, add some classes in charge of the artifacts and
bundles's persistence;
And, use the writeObject method to persist the object to a file instead of
using a XML file, the efficiency is higher. Although the object file is
difficult to understand and unmodified compared to XML file, I think the
persistence file is no need to modify manually.
> Using the new APIs to manage the bundles status both in GEP and Server side
> ----------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-759
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-759
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0
> Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6,
> Eclipse3.6SR1&SR2
> Reporter: Yi Xiao
> Assignee: Jarek Gawor
> Labels: OSGI, bundle
> Fix For: 3.0
>
> Attachments: OSGIBundleDeploy.patch,
> OSGIBundleDeploy_759_persistence.patch, OSGIBundleDeploy_changeAPI.patch,
> OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch
>
>
> This improvement depends on the server's modules, so, if the server side does
> not update timely, it may cause the GEP compile failure!
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
