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.
We've implemented the FFJ branding of the IgnorePackages.properties file and successfully built a kit without transparent persistence. I tested the handling of deserializing setting from a Pilsen installation, the ProjectErrorManager is ignoring all the ClassNotFoundException related to the persistence package. However, I am still seeing quite a few warning popups related to the TP removal. To be specific, the following are the warning messages I got:: "The popup menu for objects of type Java Source Objects could not be restored; using default settings." "The popup menu for objects of type Database schema objects could not be restored; using default settings." "com.sun.forte4j.persistence.internal.ui.modules.mappinp.MappingDataObject"
From the off-line communication with Peter, steps to reproduce the problem: Actually, it happens after I imported the setting from a Pilsen installation containing TP related stupp and when the IDE is coming up. However, it does seem to happen right before the ProjectErrorManager swallowed all the ClassNotFoundException. As for reproducing it, this is what I did: 1. Install Pilsen FCS 2. Create a new package 3. From the package, run New->Databases->Database Schema 4. You will need to have a database table in your database. Import the table. 6. From the database schema just created, call Generate Java 7. Make some changes on the wizard page "Customize Options [2 of 4]" 8. Click on "Save as default". That should save something into the settings. 9. Finished Generate Java. 10. Install the latest Orion kit. 11.On startup, import the setting from the Pilsen installation. Note that there are actually some exceptions during this steps, too, but it doesn't look like its TP related. After the import, during IDE initialization, you should see the warning popup.
I expect the problem to be in TP adding actions to JavaDataLoader and DBschema DataLoader. Those actions cannot be found and warning is displayed. I expect the code to be in org.openide.loaders.DataLoader so it might be hard to workaround...
Yarda is right in his expectatioins. This is realy the problem of TP actions plugged in JavaDataLoader and DB loader. Fortunately, DataLoader implementation doesn't display the message, but collects all exceptions as annotations and throws them at the end. I will do the same in core's LoaderPoolNode deserialization, which should solve the problem. Peter, please, verify it with Orion and TP, it worked when I simulated it with junit module and Netbeans code from release33. LoaderPoolNode.java: 1.51.14.2 fixed in release33
Resolved for 3.4.x or earlier, no new info since then -> verified
Resolved for 3.4.x or earlier, no new info since then -> closing.