Yes, something is coming back from the ML database: If I do
something like this:
<xq:execute var="results">
<xq:query>
for $i in cts:search(doc()//article-title,"$
{param.query}") [1 to 15]
return $i/root()
</xq:query>
</xq:execute>
<ol>
<c:forEach var="item" items="${results.items}">
<c:out value="${item.string}" />
</c:forEach>
I get what looks like well-formed XML. I thought I could feed that
into the JSTL XML parse routine as a string but that doesn't seem to
work. I'll try moving the ML XQuery to the server and referencing it
in the JSTL XML parse tag via a URL to see if that makes a difference.
Alan
On 4-Apr-07, at 11:50 AM, Griffin, Matt wrote:
I think that [#document: null] output means that the database
returned a
document, but it has no uri. From what I've seen, this is always what
you get when you generate a document on-the-fly with xquery.
-Matt
-----Original Message-----
The [#document: null] means your database query is returning an empty
set: it's not working?
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
