so you want to configure your cocoon components through web.xml because you don't want customers to open your cocoon webapp directory, is this correct? But if they configure through a different webapp then they would need to open a different webapp directory anyway and edit the file there. So is the point then actually more to protect customers from looking at your cocoon app?

I am not following you here, probably due to me having a slow day. Can you explain a bit more?

Jorg

Ivo Limmen wrote:

No that is not an option for a real deployment as the Java Servlet guru's have in mind.

Jorg Heymans wrote:

I really mis this option in Cocoon. I would like to deploy a war file that contains Cocoon and my generators and transformers. And I do not want the customer to open up the Cocoon web directory and change a property file to change a setting.

Does anybody know any other options?


Is providing a web based form that allows to change your component parameters an option?


Thanx,




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