> From: Sylvain Wallez [mailto:[EMAIL PROTECTED]]
<snip/> > I have seen Cocoon newbies really frightened by the lengthy > <map:components> section full of class names that starts the sitemap. > When they finally arrive at <map:pipelines>, their mindstate is such > that they hardly perceive the simplicity of the language. Can I then suggest something? Is it meaningful to move Cocoon built-in component declarations into cocoon.xconf (preserving ability to declare them in sitemap, of course)? Then sitemap will be greatly simplified, and sitemap from "chello.war" could be as simple as several lines. Are there issues with this approach? > Using hints in the sitemap is just like using "jdbc" or "j2ee" in the > "datasources" section of cocoon.xconf : hints avoid explicitly naming > the class, but their name identify their functionnality. BTW: I'm not against hints in sitemap... Vadim --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
