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: | DOMFactoryImpl causes tests with core.jar in classpath using JAXP to break under JDK 1.5 | ||
---|---|---|---|
Product: | platform | Reporter: | Jesse Glick <jglick> |
Component: | -- Other -- | Assignee: | Petr Nejedly <pnejedly> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | jchalupa, ttran |
Priority: | P1 | Keywords: | REGRESSION, T9Y |
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 41925 | ||
Attachments: |
Demonstration of failure under JDK 1.5
Same test passing on JDK 1.4 |
Description
Jesse Glick
2004-08-12 18:24:51 UTC
Created attachment 16787 [details]
Demonstration of failure under JDK 1.5
Created attachment 16788 [details]
Same test passing on JDK 1.4
Petr N: working on it? Is this beta1 stopper? The user impact is unclear to me. Jesse, do you think this is a "must fix" for Beta 1? Has a bug been filed against JDK? > Petr N: working on it? Yes, for now I have at least removed the registrations. > Is this beta1 stopper? Shouldn't be. It manifests itself only in tests, more specicifally when there is a factory registered on app classpath (note: neither the factory nor the core itself is on app classpath in NB, they are both deeper) Note: It was both compilable and working on my copy of 1.5 JDK. Oh well, it was a bit outdated. I think we'll need to add a requirement to download latest subsubversion of JDK before commit-validating... I haven't filed a JDK issue yet (hard to run remote-X bugtraq from WFH). It is manifested in tests - making it impossible to run many unit tests under JDK 1.5, which is a serious problem of course. It would also be manifested in any app based on a subset of the NB platform, i.e. using core.jar as a simple library. It is not (AFAIK) manifested in the IDE nor in the proper platform, i.e. using the regular module system and file layout and launcher. I don't see it as a beta stopper. BTW possible workaround: catch FactoryConfigurationError (or whatever it is) and try to fall back to known factory class names: Crimson, Xerces (original packaging & 1.5 repackaging). no further comments to this - closing. feel free to reopen |