prevent release of the current version.
Here's one of my pet issues that I would add to such a list:
XPathQuery/ResourceSet Design Limitations
No bug report on this, but I consider it a major outstanding issue.
See Thread "XPathQuery/ResourceSet Design Limitations?" on xindice-dev:
http://marc.theaimsgroup.com/?t=103276252300001&r=1&w=2
I use the embedded version exclusively and it was easy to make
a LazyResourceSetImpl to replace the original ResourceSetImpl
to avoid trying to stuff the entire result set into a single String.
The LazyResourceSetImpl returns the Resources one by
one through its iterator. I am willing to share this code, but
have shied away from it so far because it will require additional
effort to implement something similar for the XMLRPC version.
-Terry
Kevin O'Neill wrote:
I've been adding more unit tests and the number of bugs is growing. Most of the bugs I've created tests for are to do with our handling of xpath queries and although I can see a way forward it would involve a number of internal changes to the way we process results (for example not assuming that results from xalan are nodesets).So the question is ... do we fix these things for 1.1 or do we create a known issues list? I'm unsure. The must not be effecting too many people as the code at the root of the issue is from the 1.0 days. On the other hand I hate the thought of releasing with known issues. I want to get onto support for xquery and some other things that I've been playing with, but I'm reluctant to start until we've released 1.1. Thoughts, guidence? -k.
