The URL problem is fixed in the xercer 2.5 release. Replacing the jars
xercesImpl.jar and xmlParserAPIs.jar in testsuite\lib fixes the
problem.
Although, there still is the problem with expected values not
*literally*, but only semantically matching received values as described
below. What to
juergen 2003/10/30 03:42:53
Modified:
testsuite/testsuite/junit/xmltestcases/ACL/functional/Principle/EitherReadorWrite
ACLDenyWriteLockColFile.xml
Log:
robustness: if the acl command fails, unlock the resource again (with the right lock
token).
I suppose it is intended. Stores get resolved over the Uri class and
will be enlisted into the current transaction only if they not already
are. So, there should be no problem.
Although not completely on topic, have a look at:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=2117
