I don't have a strong opinion either so if no one wants to protest we'll
go with Jeremias's suggestion.
http://www.xmldb.org/xapi/ResourceSet";
collectionURI="driver:/path/to/collection">
...
On We
I prefer the wrapped version over the polluted :) version, but don't
have a strong feeling either way. Both are relatively easy to process.
-- Ron
Jeremias Maerki wrote:
>
> I agree. Are there other oppinions?
>
> An idea that comes to my mind is to provide an org.xml.sax.XMLFilter
> implementa
:
>
> >> Here's another alternative. I think I like this one better. By default
> >> collectionURI is only set on the root but if you need it you can also set
> >> it on a child node.
> >>
> >> http://www.xmldb.org/xapi/ResourceSet";
>
on a child node.
http://www.xmldb.org/xapi/ResourceSet";
collectionURI="driver:/path/to/collection">
...
Looks good to me except that I'd prefer an xapi:resource wrapper around
. That would help to keep the resources "clean" f
> Here's another alternative. I think I like this one better. By default
> collectionURI is only set on the root but if you need it you can also set
> it on a child node.
>
> http://www.xmldb.org/xapi/ResourceSet";
> collectionURI
Here's another alternative. I think I like this one better. By default
collectionURI is only set on the root but if you need it you can also set
it on a child node.
http://www.xmldb.org/xapi/ResourceSet";
collectionURI="driver:/path/to/collection">
...
On Satur
> What are your thoughts on adding a getResultsAsResource() method to
> ResourceSet? This is something we've been asked for in the dbXML project
> as a way to return all results as a textual XML document. Returning it as
> a Resource enables you to get the results in whate
What are your thoughts on adding a getResultsAsResource() method to
ResourceSet? This is something we've been asked for in the dbXML project
as a way to return all results as a textual XML document. Returning it as
a Resource enables you to get the results in whatever form you want. Thi
> > A cool side effect of this will be that listResources() in Collection
> > will then probably return a ResourceSet, too, so I will have a
> > ResourceIterator there.
>
> I still think listResources should return an array of strings. There are a
> lot of times where
On Thursday, August 2, 2001, at 01:05 AM, Jeremias Maerki wrote:
As the new return type for the XPathQueryService.query() method I'm
considering adding a ResourceSet. This has been requested by several
people to have more flexibility in handling the results. This would be
part of the base pa
> As the new return type for the XPathQueryService.query() method I'm
> considering adding a ResourceSet. This has been requested by several
> people to have more flexibility in handling the results. This would be
> part of the base package.
>
>
As the new return type for the XPathQueryService.query() method I'm
considering adding a ResourceSet. This has been requested by several
people to have more flexibility in handling the results. This would be
part of the base package.
interface ResourceSet {
ResourceIte
12 matches
Mail list logo
