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.
Summary: | ClassNotFoundException: JAXBException with jdk 6u4 | ||
---|---|---|---|
Product: | platform | Reporter: | mgoe <mgoe> |
Component: | Module System | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | jtulach |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Module suite project showing the issue. |
Description
mgoe
2008-01-17 16:05:57 UTC
Created attachment 55209 [details]
Module suite project showing the issue.
I added a module suite project which shows the problem. Just select File>JAXBAction to trigger the Exception shown in my bug report. reassigning to pnejedly - isn't it caused by the warmup cache? also CC'ing Jarda. Maybe he fixed in issue 125655. Anyway, please evaluate it. This is P1 that is considered to be stopper for 6.1 M1. It needs to be evaluated/fixed ASAP thank you Hardly related to startup cache - the user runs NB6.0, not a dev build. You cannot currently use the JRE's version of these classes. You must include JAXB in a lib wrapper module and depend on it. *** This issue has been marked as a duplicate of 96711 *** I don't think that it is a good idea to suppress the jre provided classes for several reasons: 1. Bugs If there is a bug in a class normally provided by the jre but replaced/suppressed by netbeans you will not be able to write a bug report against the jre. The jre people will always reject bug reports for classes not contained in the jre because the jre has been tested with the classes it contains. 2. License issues Even for a lawyer it is sometimes very hard to find out if you are allowed to extract some jars from a project and use them in another project. For that reason I don't want to use classes from an external source if they are present in the jre. 3. Endorsed dirs mechanism There is an established way to replace classes in the jre with newer ones using the endorsed dirs mechanism. Why reinvent the wheel? 4 Documentation issues Where is the documentation of the classes suppressed by netbeans. Who will decide which classes should be suppressed. For the reasons mentioned above I would like to have a netbeans platform which per default does not alter the jre in any way. If a developer requires changes the developer should be forced to switch on these changes manually for example by a property. Best regards, Martin Goettlicher See issue #96711. x *** This issue has been marked as a duplicate of 125655 *** This issue had *4 votes* before move to platform component |