>> TREGAN Fabien wrote (...) >Sorry, I don't get your point. Can you elaborate a litte bit on this? > >Carsten >
Ok : Cocoon is rather new to me, and I spent many time coding ASP ( don't laught, that's not funny) "webapps". One on the more recurrent problem for deploying ASP solution I hade was that each developper assumed that the .dll he used (and the precise version he wanted) was a "common" library and that every server hade it installed. So, when I saw that cocoon allowed per subsite (ie : per cocoon-app) configuration of component, the first thing I did was to create a new xmap with the component _I_ thought standards, so every of my next xmap will start as a copy of this one. This way, deploying one of my applicaiton on an existing cocoon server will be done in two step : adding 1 mount, then untaring 1 directory. I think this is a reason why the xmap provided with cocoon should be as simple as possible : 1- it will provide a good 'starting' xmap 2- if it's simple enough (only default generator, transformer and serializer ?), we can hope that cocoon-app will try to use a serializer that has been removed from the main xmap. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
