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 23167 - Exception is shown when working with CORBA nodes in Runtime
Summary: Exception is shown when working with CORBA nodes in Runtime
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: corba (show other bugs)
Version: 3.x
Hardware: PC All
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
: 25140 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-05-06 17:01 UTC by David Kaspar
Modified: 2003-06-30 17:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Exception (7.23 KB, text/plain)
2002-05-06 17:02 UTC, David Kaspar 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Kaspar 2002-05-06 17:01:10 UTC 
How to reproduce:
Try to expand CORBA Naming Service or CORBA
Interface Repository node in Runtime tab in Explorer
In the attachment there is shown exception.
Comment 1 David Kaspar 2002-05-06 17:02:02 UTC 
Created attachment 5656 [details]
Exception
Comment 2 Tomas Zezula 2002-05-06 18:27:28 UTC 
The bug is in cvs HEAD only.
The bug is caused by replacing xerces XML parser by new one, which
causes extrnal library to throw ClassDefNotFoundException.
The possible solutions of these bugs:
1. Integrate new openorb implmentation: (7 days included tests)
     Create JDK specific bootstrap lookup
     Change IDL compiler to deal with VB4.0
     all other NetBeans fixes (GIOP, CodeSets, recursive
TypeCodes)should be already accepted by OpenORB developers.
2. Fix the current IDE openorb implementation (3 days included tests)
3. Use JDK 1.4 ORB, can not be used on JDK 1.3 => not acceptable.
Comment 3 Tomas Zezula 2002-06-03 10:58:58 UTC 
Fixed in OpenORB extenal library.
Affected file: src/main/org/openorb/CORBA/kernel/Config.java
Change: rewritten to use Java API for XML instead of depending on
Apache Xerces XML parser.
Comment 4 Tomas Zezula 2002-06-26 13:31:13 UTC 
*** Issue 25140 has been marked as a duplicate of this issue. ***
Comment 5 David Kaspar 2002-07-08 14:18:05 UTC 
Verified
Comment 6 Quality Engineering 2003-06-30 17:08:02 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.