Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 48155 - Add ability to persist objects for a plugin / project
Summary: Add ability to persist objects for a plugin / project
Status: RESOLVED DUPLICATE of bug 36965
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-05 09:21 EST by Thorsten Schäfer CLA
Modified: 2003-12-09 13:36 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Schäfer CLA 2003-12-05 09:21:31 EST
Often plugins need to maintain state at plugin level or per project. Projects 
allow to save project properties - but it's only possible to save strings 
there. Because I think that saving state is a common task for most plugins, I'd 
appreciate if there's a possibility to save objects for a plugin/project 
without having to implement the persistence mechanism. E.g. the platform could 
support the XML (de-)serialization of objects.
Comment 1 Rafael Chaves CLA 2003-12-05 11:21:26 EST
Plugins can obtain a per-project private metadata area with
IProject.getPluginWorkingLocation. 
Comment 2 Thorsten Schäfer CLA 2003-12-05 12:41:19 EST
Yes, I know, but I think it would be useful to have a framework service for 
persisting objects instead of implementing a persistence service in every 
plugin.
Comment 3 John Arthorne CLA 2003-12-09 13:36:07 EST
JDK 1.4 already includes JAXP APIs for (de)serialization of XML.  I'm going to
mark this as a dup of the user settings plan item, which may include API for
storing richer per-project settings.

*** This bug has been marked as a duplicate of 36965 ***