Hi Oshani, I actually committed the changes you need to the WODEN-40 branch I'm working on. I've just been looking at the trunk and there is a unit test failing there. Despite this I will apply the 'speedup' changes to trunk anyway.
Cheers, Jeremy On 7/7/06, Jeremy Hughes <[EMAIL PROTECTED]> wrote:
On 7/7/06, Oshani Seneviratne <[EMAIL PROTECTED]> wrote: > Hmm.. I still get those figures. By the way I'm working on a P4, 2GHz, > 512MB Ubuntu box. Network speed could also be a culprit here. > Actually, I was wondering why these test cases are not included as > 'offline' resources in the test folder or somewhere. The real solution to this is for Woden to support an entity resolver and for that to use an XML catalog. However, I have an admission to make ... I have an interim workaround which may improve the download speed somewhat. I achieved the 40 sec value using the code out of Woden SVN. I have a modification which will use a local CVS checkout of the W3C test suite. I did this because I thought *40* secs was too much. However it only really saved me a few secs. The change may work better for you. Until now I didn't think it worth committing, but maybe it will be useful to you so I will. > That would make > it easy for anybody who is trying to test it offline or has a very > poor network speed like me:). When you see the commit message do an svn update and let me know whether it improves things for DOM. It should actually improve StAX/OM too. > > Anyway, the StAX/OM version should run much faster than the DOM > version, and I would like to hear the results you get on this too. Sure will do. Cheers, Jeremy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
