Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <27AFC41AECE2D4118FA000D0B7C57054148539@mx02.wide.com>
From: Rob Moffat <Rob.Moffat@widelearning.com>
To: "'cocoon-dev@xml.apache.org'" <cocoon-dev@xml.apache.org>
Subject: RE: Bug in TraxTransformer resolve()?? 
Date: Thu, 7 Jun 2001 10:15:08 +0100 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"

Cheers for having a look at this problem!  Having solved this, cocoon2 and 
my URL factory appear to work correctly as a webapp and I have no need to 
extend supported protocols with -Djava.protocol.handler.pkgs... (messy)

excellent work - cheers,

rob 

-----Original Message-----
From: Carsten Ziegeler [mailto:cziegeler@sundn.de]
Sent: Thursday, June 07, 2001 10:07 AM
To: cocoon-dev@xml.apache.org
Subject: AW: Bug in TraxTransformer resolve()?? 


Sorry, Rick, for the long delay.

Yes, great that is exactly the problem. I applied your patch
and now everything works fine!

And of course you are right, if the resolve() method only
returns an input stream, Xalan is not able to know the base.
So it's really not a Xalan bug.

Great! So, the special cocoon urls will also work inside
the stylesheets.


Carsten 

Open Source Group                        sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de                          mailto: cziegeler@sundn.de 
================================================================

> Rick Tessner wrote:
> 
> On Fri, 01 Jun 2001 09:20:44 +0200, "Carsten Ziegeler" wrote:
> 
> >I just checked some ideas to make it at least work, but unfortunalety
> >Xalan prevents us from a working version.
> >So, to avoid any problems with the XSL specification, we can't use
> >the cocoon urls in xsl:include etc for now. When the problem in Xalan
> >is fixed, we can use it.
> 
> Hi Carsten,
> 
> I think I found a solution to this ... I'm not so certain anymore
> that this is a xalan issue.
> 
> I've attached a patch that through some preliminary testing seems
> to work.  It hasn't been extensively tested by any means since
> I'm not aware of all the issues surrounding the URIResolver bits.
> 
> This fix basically includes the URI along with the InputStream
> in returning the javax.xml.transform.stream.StreamSource from
> the resolve() method.
> 
> With this, the "base" parameter is no longer being passed in
> as null.
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org