[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
RE: Re: [xml-dev] What should TrAX look like? (Was: Re: [xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
- To: "Michael Kay" <mike@...>,"Prakash Yamuna" <techpy@...>,<xml-dev@...>
- Subject: RE: Re: [xml-dev] What should TrAX look like? (Was: Re: [xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
- From: "Dare Obasanjo" <dareo@...>
- Date: Mon, 21 Feb 2005 14:11:36 -0800
- Thread-index: AcUV/ei1eCRsshPZSY+llP9DXvxQiQAAPH0gAAOHvQAAKwn3UA==
- Thread-topic: Re: [xml-dev] What should TrAX look like? (Was: Re: [xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
And if you pass it
public class EmptySource implements Source{
private String systemId = "http://www.example.com/myidentifier";
public void setSystemId(String systemId){ this.systemId =
systemId; }
public String getSystemId(){ return this.systemId; }
}
what does it do? After all this class faithfully implements the Source
interface.
--
PITHY WORDS OF WISDOM
There is always one more bug.
-----Original Message-----
From: Michael Kay [mailto:mike@...]
Sent: Friday, February 18, 2005 2:58 PM
To: Dare Obasanjo; 'Prakash Yamuna'; xml-dev@...
Subject: RE: Re: [xml-dev] What should TrAX look like? (Was: Re:
[xml-dev] Article on JAXP 1.3 "Fast and Easy XML Processing")
> Translation: Source isn't any more useful than just using
> java.lang.Object
There is one advantage. If you hand the transform() method a Date, or a
List, or a Gremlin, you will get a compile time type error. For me,
that's a good enough reason to invent a marker interface rather than
using Object.
Michael Kay
http://www.saxonica.com/
|
