This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 244586

Summary:	Re-/Storing TopComponent persistence from a database
Product:	platform	Reporter:	Jerome_Oe
Component:	Window System	Assignee:	Stanislav Aubrecht <saubrecht>
Status:	NEW ---
Severity:	normal
Priority:	P2
Version:	8.0.1
Hardware:	PC
OS:	Windows 7
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Jerome_Oe 2014-05-19 11:14:30 UTC

It would be nice if it would be possible to store the persistence of TopComponents in a database and not in the local FileSystem.

The benefit would be an user specific persistency, independent from the machine on which the user has logged in.

If the user has logged in, his TopComponent configuration will be loaded from a database so that the user has always the same feeling of the application.

I know about the Roles API. In case of singleton TopComponents it's really nice but not with dynamically generated TCs. Also Roles API restricts to predefined modes, that is not wanted! Wanted is a feeling of total freedom for the user.


A suggestion is to add a readFromDatabase and a writeFromDatabase- method to the PersistenceManager(or even in a better place) and also a possibility to overrite them.

Eventually there have to be some restrictions on how the persistence files are stored in the database so that the PersistenceManager could easily generate his modestructure out of it.


Kind regards!