Wolfgang Jeltsch schrieb:
Am Freitag, 13. Juni 2008 16:39 schrieb Andreas Hartmann:
[…]
I'd start with this tutorial:
http://lenya.apache.org/docs/2_0_x/tutorials/newpublication/index.html
Some details might be outdated, if something doesn't work don't hesitate
to complain.
I complain.
First, I don’t understand why access control data isn’t held inside the
publication directory like it seems to be the case with the default
publication. Is this for sharing authentication data between publications?
No, the separation of application and data is meant to simplify maintenance:
- easier backup of data
- convenient if you store the data in SVN
- you can deploy the webapp as a WAR file
- easier handling of file system permissions
Does such a sharing work reliably by just using the same access control data
directory for different publications or are there synchronisation issues?
It shouldn't make a difference whether the data are shared across
publications. AFAIK the ItemManager service objects are created per
directory and not per publication, so if two publications share the same
data directory, they share the same ItemManager object. So, if
synchronisation issues occur, they could also occur in a single publication.
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;
}
Third, if I click on „My First Publication“ as told at the end of the
tutorial, I don’t get the introduction page but a page with the following
content:
Resource Not Found
Message: Resource Not Found
Description: The requested resource "/fcgs/introduction.html" could not be
found
I'll try to take a look at it as soon as I find the time.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
