Ahh yes you are correct. I've been using a modified XInclude transformer that uses a custom URI class to better handle uri's supplied via the href attribute. This modified version correctly handles relative/absolute URI's (including the Cocoon custom protocols.) I haven't submitted it back to the Cocoon community yet because I haven't fully documented/tested it, but it does work. You are welcome to test it out. I've attached the necessary source files you'll need to this message. Let me know what you think.
Regards, --mike On Wed, 21 Nov 2001, Stephan Michels wrote: > > > On Tue, 20 Nov 2001, Michael McKibben wrote: > > > Also, don't forget the parse="xml" attribute on your xinclude element. I > > didn't see it in the original example you sent. > > > > I thought this were the default. > > From XInclude.java(87): > if (null == parse) parse="xml"; > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> >
XIncludeTransformer.java
Description: Binary data
MalformedURIException.java
Description: Binary data
URI.java
Description: Binary data
--------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
