Reinhard Poetz wrote:
AFAIR due to the fact that resource:/ protocol is not as functional as file:/ (no directiories?) and it would be quite intensive operation to find .xconf files.Daniel Fagerstrom wrote:Leszek Gawron wrote:Reinhard Poetz wrote:Should we move the stylesheetsI would help a lot to be able to deploy cocoon with no additional files at all. What do you say if we moved cocoon logo and default stylesheets (the ones styling error pages etc.) to some jar (either existing or a new one)?A new one. IMO we should move away from the monolitic thinking and start to think in terms of pluggins/bundles/blocks. Making the minimal Cocoon really lean would help using it embeded in new and innovative contexts, http://marc.theaimsgroup.com/?t=111366405100002&r=1&w=2.This way we can have cocoon that consists of: - bunch of .jar files - web.xml which hardly changes - a set of .xconf and logkit files.+1It's a pity we cannot move .xconf files into jars.Why can't we?
theoretically we can but soon we will have .cob files that *are* single files. So for now *I* wouldn't invest too much work.
What will cocoon core consist of then? I mean file types.. -- Leszek Gawron [EMAIL PROTECTED] Project Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
smime.p7s
Description: S/MIME Cryptographic Signature
