| Bug in eclipse xerces parser - who can help? [message #119689] |
Sat, 30 August 2003 05:29  |
Eclipse User |
|
|
|
Hi, I am not sure whether this is the right place to post this problem but
I didn't see any better forum.
I am using the xerces parser from eclipse 4.0.7 and encountered into a
problem with the XMLSerializer, which has also been reported to the apache
forums (bug 21404 - Elements that have long text as the text node content
are serialized with a line break and additional indentation).
I cannot use the proposed workaround by overriding the printText methods
since they have been declared as final in the eclipse version.
On the other hand I need to use the eclipse version because I am using the
property to set the external-schemalocation which is not working properly
with any of apache xerces 2.3.x+ releases that I have tried.
Is there any newer version of the eclipse xerces parser where this problem
has been fixed?
Where can I find the sources of the eclipse xerces to change the method
declaration and use the workaround .... are they included in the eclipse
sources?
Or can I use the XMLSerializer class from apache.org ... is this working
with the other eclipse xerces classes?
Thanks in advance for any help.
Michael
|
|
|
|
|
| Re: Bug in eclipse xerces parser - who can help? [message #123546 is a reply to message #123432] |
Sat, 06 September 2003 01:06  |
| Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
"John Arthorne" <John_Arthorne@oti.com_> wrote in message
news:3F58F3AB.7020309@oti.com_...
> I don't think it's quite that bad. You can't put a conflicting xerces
> on the boot classpath or in your JRE's "ext" directory. I'm fairly sure
> you can put your own private xerces in your plugin and load it in the
> normal way without playing with class loaders though.
I'm fairly sure you can't.
> The plan item to
> remove the core platform's dependency on xerces should address these
> problems:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=37696
I keep hoping. It's not obvious from the comments on the bug, or from your
comment just now, that we all agree on what the problem is. :-(
Bob
> --
>
> Bob Foster wrote:
> > You're kind of in a pickle. Eclipse uses out-of-date versions of Xerces
> > dropped off at random times from somebody in IBM (probably on the xml4j
> > team, but I've never confirmed that). Then, to make matters worse,
Eclipse
> > uses its out-of-date Xerces in such a way that it interferes with all
> > plugins' use of Xerces. You can't even put your own version of Xerces in
a
> > jar along with your plugin without writing your own classloader to load
it.
> > There is an active bug on the subject, but that probably won't help you
> > anytime soon.
> >
>
|
|
|
Powered by
FUDForum. Page generated in 0.03586 seconds
Home