Boris Kolpackov wrote:
Otherwise, I'm happy with the string pool syncing work-around.
Yes, I think this is the easiest fix for the time being (I've
already sent a patch to xqilla-users).
This seems like the best fix for the moment. I'll commit it soon.
John
--
John Snelson, Oracle Corporati
Hi John,
John Snelson <[EMAIL PROTECTED]> writes:
> In XQilla the grammars are copied from the DOMBuilder to an
> XMLGrammarPool owned by the DOMXPathExpression to make them accessible
> in a thread safe manner. Looking at the DOM 3 specs, nothing is said
> about the thread-safety of DOMXPathExpr
Hi Boris,
Thanks for looking into this problem for me.
In XQilla the grammars are copied from the DOMBuilder to an
XMLGrammarPool owned by the DOMXPathExpression to make them accessible
in a thread safe manner. Looking at the DOM 3 specs, nothing is said
about the thread-safety of DOMXPathExp
Hi John,
John Snelson <[EMAIL PROTECTED]> writes:
> I realise I'm probably doing things that most people won't ever need to
> do with Xerces-C. Never-the-less is what I'm trying to do valid, and if
> so is the IllegalArgumentException a bug in Xerces-C?
I think what you are doing is valid howeve
Hi,
In the course of working on XQilla, I've been getting an
IllegalArgumentException when I'm using the XMLGrammarPool with Xerces-C
2.8. Boris brought this to my attention, and it's slightly odd since it
only seems to occur with attribute groups in schemas. I've attached
sample code, XML an
