> -----Original Message-----
> From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 31, 2001 6:27 AM
> To: [EMAIL PROTECTED]
> Subject: RE: (sub)sitemap context
> 
> I can take care of this then...
> 
> The only question is: shouldn't the sitemap itself set
> it's context path depending on the sitemap's file path

Wait here for a second: URI space where sitemap is mounted could be
different from the physical location on the disk. Please do not mount
sitemap based on directory it is located in. For sub-sitemaps, we have
two attributes: URI-prefix and sitemap file (or directory where it is
located).

Vadim

> or should the creator prepare the context with the
> appropriate working dir?
> --
> Torsten
> 
> > -----Original Message-----
> > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, October 31, 2001 11:44 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: (sub)sitemap context
> >
> >
> > Right!
> >
> > This is a bug!
> >
> > Carsten
> >
> > > -----Original Message-----
> > > From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
> > > Sent: Wednesday, October 31, 2001 10:47 AM
> > > To: Cocoon-Dev
> > > Subject: (sub)sitemap context
> > >
> > >
> > > Has anyone ever tried to put the root sitemap somewhere
> > > deeper into a subdirectory in the servlet context ?
> > > Unfortunately the sitemap context does not change as expected.
> > >
> > >   cocoon.xconf:
> > >   <sitemap file="subdir/sitemap.xmap" ../>
> > >
> > > Sitemap context is still "/" what of course makes
> > > the sitemap look at all the wrong places.
> > >
> > > I think it is more consistent to behave like the
> > > usual sub sitemap mounting. Sitemap context should
> > > be the directory the sitemap is really in.
> > >
> > > Right?
> > > --
> > > Torsten
> > >
> > >
---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> > >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to