Am Sonntag, 22. Juni 2008 20:01 schrieb Andreas Hartmann:
> Wolfgang Jeltsch schrieb:
> > Am Montag, 16. Juni 2008 11:28 schrieb Andreas Hartmann:
> > > Wolfgang Jeltsch schrieb:
> […]
> > But look at the directory structure in the section “Prerequisites”. All
> > access control data is meant to be stored under
> > $HOME/src/lenya/data/access-control. The publication name isn’t
> > mentioned in this path. So if I would create a second publication
> > according to the same scheme, its access control data would be stored in
> > the same path.
>
> In this case you can just add another directory to the hierarchy:
>
> $HOME/src/lenya/{pub}/data/…
Yes, but this should also be done in the tutorial, otherwise it is misleading.
> […]
> >>> Second, I don’t know how Lucene knows to what base directory the
> >>> relative paths in lucene_index.xml refer. The example lucene_index.xml
> >>> contains paths starting with lenya/pubs/$MYPUB.
> >>
> >> IndexManagerImpl:370
> >>
> >> if (!directory.startsWith(File.separator)) {
> >> directory = getServletContextPath() + File.separator + directory;
> >> }
> >
> > But this would mean that the servlet context path would have to be
> > $HOME/src while lenya is installed in $HOME/apache/lenya-2.0.
>
> Hmm, why should that be the case?
>
> With Jetty, the servlet context is $LENYA_HOME/build/lenya/webapp.
> If you deploy to Tomcat (using /lenya as servlet path), the servlet
> context is $TOMCAT_HOME/webapps/lenya.
I’m talking about the directory layout used in the tutorial (at
<http://lenya.apache.org/docs/2_0_x/tutorials/newpublication/index.html>).
Lenya is installed there in $HOME/apache/lenya-2.0. The Lucene indexing
stuff is intended to go into $HOME/src/lenya/pubs/$MYPUB/work/lucene/index.
The paths in lucene_index.xml start with lenya/pubs/$MYPUB/work/lucene/index.
So the base directory should be $HOME/src. I doubt that this is the servlet
context path. So the tutorial should probably be corrected at this point.
> […]
Best wishes,
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
