cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@dff.st>
Subject RE: xinclude sitemap
Date Fri, 08 Dec 2000 12:03:35 GMT
> Ah, you've gone one step beyond me - I've not tried to combine
> xinclude with
> xsp.  I *think* that the processing order might be the problem.
> Try getting
> a plain xml (no xsp) xinclude to work first.
>
> <util:include-uri> doesn't exist in C2 yet.  I've encountered the prob but
> have yet to create the logicsheet.
>
> Try the plain xinclude, then we can try and get it to work with xsp.

Gonna try it..

>
> John.
>
> PS, reply to the mail list - more people than just us are prob interested!

I'm always wondering if such questions are more "users" questions or "dev"
questions. So I'm a bit restrained about posting to cocoon-dev.
(But cocoon-users is more about C1. Having a cocoon1-users/dev and
 a cocoon2-users/dev list would be better)
--
Torsten


> > -----Original Message-----
> > From: Torsten Curdt [mailto:tcurdt@dff.st]
> > Sent: 08 December 2000 10:07 am
> > To: John.Morrison@uk.experian.com
> > Subject: RE: xinclude sitemap
> >
> >
> > > I just (yesterday) had the same problem.  If you're moving xml
> > > over from C1
> > > to C2 you have to revert back to the old spec of defining
> > xincludes...
> > >
> > > instead of:
> > >
> > > <mytag xinclude:parse="xml" xinclude:href="xxx"/>
> > >
> > > you need:
> > >
> > > <xinclude:include parse="xml" href="xxx"/>
> > Thanks for your reply! Still doesn't work though ;(
> > Maybe you could have a look...
> >
> > Now I tried it this way:
> >
> >   <?xml version="1.0" encoding="ISO-8859-1"?>
> >   <xsp:page language="java"
> >             xmlns:xsp="http://apache.org/xsp"
> >   >
> >     <page xmlns:xinclude="http://www.w3.org/1999/XML/xinclude">
> >      ...something...
> >      <xinclude:include parse="xml" href="/test/included.xml"/>
> >      ...something...
> >     </page>
> >   </xsp:page>
> >
> > With my sitemap (as I already posted):
> >
> >   <map:match pattern="test">
> >     <map:generate type="serverpages" src="test/test.xml"/>
> >     <map:transform type="xinclude"/>
> >     <map:transform src="test/html.xsl"/>
> >     <map:serialize/>
> >   </map:match>
> >
> > But all I get is
> >   ...
> >   <xinclude:include
> > xmlns:xinclude="http://www.w3.org/1999/XML/xinclude"
> > parse="xml" href="/test/included.xml"</xinclude:include>
> >   ...
> >
> > where there should be the included file!
> >
> >
> > BTW: Do you know the difference to <util:include-uri>?
> >      I was considering this, too.
> >
> > > I've looked at the xinclude transformer, but I'm (very) new to SAX
> > > programming and was unable to fix it.
> >
> > > If you would like to bring it back in
> > > line with the spec I'm sure lots of people would love you for it!
> >
> > I'm sure ;) We'll see - first it has to work the old way.
> > Then there is room for improvements ;)


Mime
View raw message