Victoria Vitaver wrote:


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 ...


Yes, exactly :)

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.

Problem is that we are placing it all in a .war file ... and unless we create an openwar file (which is what we are doing atm) we have to redeploy the full thing.


ok, so if the data could be deployed outsitde of the webapp, then you're problem would be solved



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?



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

Yes,  that would be nice :)


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 ;-)



wow  thanks :)
Otherwise if you dont get around to it .. I will try have another go next week


I will need to finish some other tasks before, but I really hope that I can do it as soon
as possible. And otherwise I will appreciate your help next week.

Michi


Vica

---------------------------------------------------------------------
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]

Reply via email to