Joerg Heinicke wrote:
> Hi,
>
> I fixed a bug in Cocoon's ZipSource lately and added a test case for it [1].
> Unfortunately for people on Mac OS X this test failed - actually not due to
> ZipSource but Excalibur's FileSource.
>
> The test is as simple as
>
> public void testURIHandling() throws Exception {
> String uri = "file://test.zip";
> Source source;
> SourceResolver resolver = null;
> try {
> resolver =
> (SourceResolver)getManager().lookup(SourceResolver.ROLE);
> source = resolver.resolveURI(uri);
> } catch (ServiceException se) {
> throw new SourceException("SourceResolver is not available.", se);
> } finally {
> getManager().release(resolver);
> }
> assertEquals("Uri is wrong.", uri, source.getURI());
> }
>
> (running in a Cocoon test environment, getManager() returns a ServiceManager).
>
> Now where is the problem? It works as expected on Windows but fails on Max OS
> X
> despite the same debug output of source resolving:
>
> [DEBUG] Resolving 'file://test.zip' with base 'null' in context ...
> [DEBUG] Resolved to systemID : file://test.zip
> [DEBUG] Creating source object for file://test.zip
>
> What seems to get wrong is FileSource.getUri() as Jorg investigated [2]. The
> question is if you want to handle this "accepted" bug in the JDK in Excalibur?
>
Sorry, but I don't quiet get what we could do to fix this (I'm lost in
too many - or too few - slashes...).
If there is something we could fix here, we should do it.
Carsten
--
Carsten Ziegeler
http://www.osoco.org/weblogs/rael/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
