[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: JAXP 1.3 for Java 1.4?

• To: Michael Kay <michael.h.kay@n...>
• Subject: Re: JAXP 1.3 for Java 1.4?
• From: Elliotte Harold <elharo@m...>
• Date: Fri, 08 Oct 2004 15:41:09 -0400
• Cc: 'Michael Good' <musicxml@y...>, xml-dev@l...
• In-reply-to: <20041008185802.EMMV24841.mta02-svc.ntlworld.com@Turtle>
• References: <20041008185802.EMMV24841.mta02-svc.ntlworld.com@Turtle>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910

Michael Kay wrote:

> It's not quite so easy. One of the new methods in DOM3 is
> getSchemaTypeInfo(), which returns an object of type TypeInfo, and TypeInfo
> is an interface that's not available in JDK 1.4. So to produce an
> implementation that compiles under JDK 1.5, I need to declare a method that
> returns a TypeInfo, and this method won't compile under JDK 1.4 because
> TypeInfo is not present. Currently, I don't see a way around this. It might
> be possible to get round it by issuing dummy versions of the JDK 1.5
> interfaces, but it's certainly very fiddly.

That is a little more complicated, but I'm still not sure it's 
insurmountable. They don't have to be dummy versions. Saxon could supply 
the genuine TypeInfo interface from the W3C. This would work in java 1.4 
without any trouble. Does Java 1.5 get upset if third part code tries to 
supply org.w3c.dom interfaces of its own? Or does it just ignore that 
and load the ones it find in the bootclasspath?

--
Elliotte

• References:
  • RE: JAXP 1.3 for Java 1.4?
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: RE: JAXP 1.3 for Java 1.4?
• Next by Date: ANNOUNCE: TagSoup 1.0rc1 released
• Previous by thread: RE: JAXP 1.3 for Java 1.4?
• Next by thread: RE: JAXP 1.3 for Java 1.4?
• Index(es):
  • Date
  • Thread