4) go to dm.dev.com to activate the web application and have the war file deploy. This should bring up the Cocoon welcome page in the ROOT of the site!
Using this technique I have a sepparate directory and Cocoon configuration for every site I run. A major advantage to my oppinion.
This has been of great help (I was stuck in the same problem :)) ... but, as you said, the whole site will be served by cocoon. Now, what about images, downloads, zip files etc ?? ... everything that does not need to be parsed should be served directly by apache (also because cocoon adds a overhead). But making the whole site a webapp this does not happen. My actual solution is to have something like "images.mysite.com" as a virtual host mapped on the same directory, accepting .gif only, but it's just a bad artifact, since i always have to give complete urls for images.
Any solution for this ? Isn't it possible to have the web app receive only some extensions? or have apache catch *.gif before the web app, or something similar ?
Thanks
Simone
