Hi Billy,
> -----Urspr�ngliche Nachricht-----
> Von: Billy L. Williams, Jr. [mailto:[EMAIL PROTECTED]
> Gesendet am: Donnerstag, 28. Juni 2001 18:19
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Xerces 1.4.1/Saxon problem
>
> Hi Frank,
>
> I don't know if you have the same thing, but we just ran into
> a similar
> situation in a Weblogic application server environment.
> Turns out that
> our appserver was setting the
> javax.xml.parsers.SAXParserFactory system
> property to a SAX 1.0 parser, and that class didn't implement
> a method
> that was added in SAX 2.0, causing an AbstractMethodError to
> be raised
> in our transformations with Saxon. We only saw a problem when we
> started to use Saxon....is this similar to your problem?
Sounds a bit alike, though my classpath was fairly clean in the end and
our application sets that particular system property to Xerces.
There was no jaxp.par and/or SAX1 parser in classpath any more
(I figure only jar the problem could have been buried could have
been saxon.jar, xerces.jar or xalan.jar).
Actually I have even more doubts in the xerces141.jar I have (binary
distribution), as I posted earlier, but none of the gurus replied yet.
Reproducing the error seems to be fairly involved and deadlines
are not really close so I figure I'll wait for 1.4.2 and hope
it will solve my concerns :-) I still think there is something
different with the jaxp classes in the xerces jars...
Thanks for asking,
Frank
Here above mentioned other difference I find between 1.4.0 and 1.4.1
(actually parts of my old mail pasted in):
I had those problems with Saxon against Xerces 1.4.1
in special circumstances. While trying to boil that down and
at the same time try to make progress with my work, I now
observe a different behaviour which also looks "kind of
interesting":
Compiling a class with the (incorrect) method.
public static XYZ parse(InputSource src)
{
SAXParserFactory spf = SAXParserFactory.newInstance();
spf.setNamespaceAware(true);
SAXParser sp = spf.newSAXParser();
XYZParser schp = new XYZParser();
sp.parse(src, (DefaultHandler)schp);
return schp.getXYZ();
}
with a cleanroom classpath, I get with xerces 1.4.0
c:\programme\jdk1.3\bin\javac -classpath .\coi.jar;.\xerces140.jar;.
schema/Sche
maParser.java
schema/SchemaParser.java:26: unreported exception
javax.xml.parsers.ParserConfig
urationException; must be caught or declared to be thrown
SAXParser sp = spf.newSAXParser();
^
schema/SchemaParser.java:28: unreported exception org.xml.sax.SAXException;
must
be caught or declared to be thrown
sp.parse(src, (DefaultHandler)schp);
^
2 errors
with xerces 1.4.1 instead of 1.4.0 I get
schema/SchemaParser.java:28: cannot resolve symbol
symbol : method parse
(org.xml.sax.InputSource,org.xml.sax.helpers.DefaultHand
ler)
location: class javax.xml.parsers.SAXParser
sp.parse(src, (DefaultHandler)schp);
^
1 error
I have no jaxp.jar in path and I'm using jdk1.3 under Win NT.
>
> Billy
>
> Nestel, Frank wrote:
>
> >Of course you need a stripped down program, but I currently only
> >have a fairly complex framework and the observation that changing
> >from Xerces 1.4.1 to 1.4.0 is unhealthy. Classpath is a know
> >problem here, but usually I manage to keep all wrong jaxp.jar's
> >out of my classpath. I have to see if I find someone to boil
> >down the problem to an reproducable piece of code. It would have
> >been easier if it had been a know issue. I didn't find it in
> >bugzilla, but I'm not confident in that way of investigation, so
> >I thought first question is free.
> >
> >Frank
> >
> >P.S.: Actually I realize that in a different application, with
> >the same framework, all seems to work. I have to dig definately
> >deeper at my side. Thanks for your patience.
> >
> >>-----Urspr�ngliche Nachricht-----
> >>Von: Edwin Goei [mailto:[EMAIL PROTECTED]
> >>Gesendet am: Mittwoch, 27. Juni 2001 01:04
> >>An: [EMAIL PROTECTED]
> >>Cc: [EMAIL PROTECTED]
> >>Betreff: Re: Xerces 1.4.1/Saxon problem
> >>
> >>[EMAIL PROTECTED] wrote:
> >>
> >>>Hi Frank,
> >>>
> >>>Looking at the Xerces source I can't see any obvious reason
> >>>
> >>why you should
> >>
> >>>get an error like this. It would be very interesting
> >>>
> >>though if you could
> >>
> >>>use the code in Saxon to rig up a freestanding application
> >>>
> >>which throws
> >>
> >>>this error.
> >>>
> >>>Basically all Saxon seems to be relying on is having a
> >>>
> >>JAXP-compliant
> >>
> >>>implementation, which we do.
> >>>
> >>>It would be really nice if Edwin could comment on this one... :-)
> >>>
> >>I just downloaded Xerces 1.4.1 and Saxon 6.3 and was not able to
> >>reproduce the problem. Could you provide a sample program?
> >>Also, what
> >>classpath did you use?
> >>
> >>-Edwin
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: [EMAIL PROTECTED]
> >For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
