[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RDDL API
- From: Michael Brennan <Michael_Brennan@Allegis.com>
- To: 'Jonathan Borden' <jborden@mediaone.net>, xml-dev@lists.xml.org
- Date: Thu, 04 Jan 2001 12:59:30 -0800
What about having the "getResource" return a javax.activation.DataSource
object rather than an InputStream? That way the content-type can be conveyed
if it is defined in the catalog.
> -----Original Message-----
> From: Jonathan Borden [mailto:jborden@mediaone.net]
> Sent: Wednesday, January 03, 2001 7:24 PM
> To: xml-dev@lists.xml.org
> Subject: RDDL API
>
>
> I think it would be fairly straightforward to write a SAX
> filter looking
> something like:
>
> RDDLFilter rdf .... oops can't use that name....
>
> RDDLParser rdp = new RDDLParser();
>
> ContentHandler ch = (ContentHandler) rdp;
>
> // hook it up...
>
> rdp.resolve(namespaceURI, arcroleURI);
>
>
> This would work for well-formed resources and perhaps we
> need something
> like
>
> InputStream s = rdp.getResource(namespaceURI,arcroleURI);
>
> for non-XML resources.
>
> Anything else needed?
>
> -Jonathan
>
>