Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [wtp-dev] Issues with Xerces

If this doesn't take care of everything, another option is to take a copy of xerces and rename all the packages in it, making that into a shared plug-in. (org.eclipse.xerces or something :). This option is mentioned here:

From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeffrey Liu
Sent: Monday, April 25, 2005 3:36 PM
To: General discussion of project-wide or architectural issues.
Subject: Re: [wtp-dev] Issues with Xerces (was:IMPORTANT: defect/build procedure this week for WTP M4)

Before refactoring Xerces into private copies. I want to say that I think I have a fix for the Web Services Explorer problem. The problem is actually in Crimson's Element.replaceChild(.....) method. I'm investigating whether the J2EE problem is a similar deal. If so, then there may be a simple change in our code that can workaround this Crimson bug... I'll report to this list asap.

Back to the top