Victoria Vitaver wrote:
Michael Wechner wrote:
Hi
I have fixed a bug re the DocumentIdToPathMapper, because within the
DefaultCreator resp. DefaultBranchCreator it was hardcoded instead
using the DocumentIdToPathMapper.
Because of that I had to slightly change the API of
src/java/org/apache/lenya/cms/authoring/ParentChildCreatorInterface.java
Hmm... also, while we are around the topic. In my project I have the
necesity to pluck out the 'content/' and the 'resources/' directories
out of the publication -
you mean to some other directory, e.g /data/lenya/content ...
Main reason - The site that we have (which is atm in staging - ready
to go live) has quite a bit of dynamic content, linked in with static
pages - lenya documents.
The development, staging and live environments are on different
servers. It would be _really_ nice to be able to follow the lenya
publishing framework on Dev/Staging and then have a usecase which just
ships over the static content into a directory - not requiring a
restart to the server.
actulally for the "live are" there should not be restart necessary,
because the sitetree is checking if the sitetree file has been changed
(because of read-only). I think in "authoring area" it's necessary,
because otherwise one get a conflict.
We thought this would be quite simple, but after experimenting and
digging around in the java code I found that the '/content' directory
is referenced relative to the servlet context (relevant files
org.apache.lenya.cms.publication: Publication.java and
AbstractPublication.java).
Is there any reason for this restriction?
not really. I actually though about this and wanted to change this
within 1.2.5-dev version ...
I also tried to fiddle around with the code and take away this
restriction but I wasn't able to get it fully working in my allocated
time(which wasnt much :p).
yes, there are several places which one needs to change that, but I
definitely think we
should centralize that and make it easy configurable, e.g. within
PUB_ID/config/publication.xconf
We are also using 1.2.3 version of lenya, with JBoss and we are more
than happy to contribute the code if I am able to get it working.
But before I have another go at it - has anyone here possibly already
figured out a way to do this?
I might implement it today ;-)
Are there fundamental flaws in trying to do what I propose?
no
Michi
Thanks,
Vica
Thanks
Michi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
