Actually Im lookign for a production build to base a customer's web site off of. There are only three beefs I have about cocoon. 1) it Doesnt have a build target for a production build. 2) it doesnt Support XForms W3C standard. 3) It doesnt use Log4j for logging.
1) is annoying but will go away after i figure it out. 2) is a bummer but I can deal with XMLForms 3) is very bad but at lease I can configure Log4j with my additions. Logging into files in the cocoon build is a far less than optimal solution in production. I would like to support JMS based XML logging. -- Robert "Upayavira" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > Robert Simmons wrote: > > >Well, I have no desire to get into the Dev list because I wouldnt need it > >for any more than this, but I can say that it is preposterous that there > >isnt a "production" target for Cocoon build. Absolutely rediculous beyond > >compare. Anyone wanting to use cocoon in a production environment is not > >going to want to merely create another subdirectory. If the developers dont > >relaize this then I have to tell them to get their heads out of academic > >land and start thinking about commercial applications of cocoon. > > > > > Robert, > > Welcome back. Haven't heard from you for a while. > > I know Cocoon isn't (yet) perfect, but I have found preparing Cocoon for > deployment to be quite managable in a production environment. And I > agree, no-one in their right minds would use the 'automounting a > subdirectory' for a professional production site. > > Unfortunately, it isn't straightforward to produce a single 'production' > build for Cocoon, as each user will require different parts of the > framework. Therefore, the compromise for the time being (and it is > recognised as a compromise) is to edit the local.blocks.properties file > (copied from blocks.properties first) and edit out the parts that you > don't want. If you are building a very simple site, then you can exclude > everything. In my build I only leave Batik, which I will be needing > soon. Also, you can exclude the samples, deprecated code and scratchpad > with the same process by editing local.build.properties (copied from > build.properties). See install.txt for more info. > > Then run the build script. The build/cocoon-2.1 folder can be ignored - > it is just used during the build process. All you need is in > build/webapp. Move that where ever you want. > > Rather than using the 'automount' feature, you can add a simple 'match > everything and mount a subsitemap, right at the beginning of the first > pipeline in the sitemap in your webapp directory: > > <map:match pattern="**"> > <map:mount src="file:/d:/path/to/your/sitemap/" check-reload="yes" > uri-prefix=""/> > </map:match> > > It can mount another sitemap from anywhere on your system. > > Thus you can build a Cocoon system that exactly matches your > requirements and that mounts a site that is external to the webapp. > > I know this process is slightly longwinded and not yet ideal, but in my > view it is better than what we had (and was, to some extent, brought > into being because of your comments previously). Major reworking that > should improve things significantly should appear in Cocoon 2.2 which > should include the proposed Cocoon blocks. > > I have found it quite manageable, having now installed this setup on at > least four computers recently (two of them production servers with live > and test environments, with the sites updated by ant directly from a CVS > repository). > > Have I missed something? > > Upayavira > > >Additionally, how bloody hard could it be to make this target? Twenty > >minutes of work for someone that knows the product? > > > >-- Robert > > > >-----Urspr�ngliche Nachricht----- > >Von: Chris Clark [mailto:[EMAIL PROTECTED] > >Gesendet: Mittwoch, 27. August 2003 14:43 > >An: [EMAIL PROTECTED] > >Betreff: RE: Empty Webapp build? > > > > > >You're not the only user that wants that. > >I asked in the Dev mailing list a couple of days ago (Subject: "Production" > >build for Cocoon). > >It touched off a little controversy... :) > > > >The advice I supplied in the first reply was more-or-less a repeat of what > >the dev's reply to me was. If you read the entire thread, there was some > >advice from another user on what you'd have to manually go in and delete. > > > >Feel free to add a post to that thread asking for a build target of > >"Production". :) > > > > > > > >>-----Original Message----- > >>From: Robert Simmons [SMTP:[EMAIL PROTECTED] > >>Sent: Wednesday, August 27, 2003 8:22 AM > >>To: '[EMAIL PROTECTED]' > >>Subject: AW: Empty Webapp build? > >> > >>Actually, I dont want to create just another directory. This is for a > >>production project and I dont want any of the cocoon docs or examples or > >> > >> > >any > > > > > >>of that. I want it totally blank. > >> > >>I find it .... strange ... that I should be the only cocoon user to want > >>that. There should be a build target. Of course I said this in February > >> > >> > >last > > > > > >>year so Id assume they would have put it in by now. > >> > >>-- Robert > >> > >>-----Urspr�ngliche Nachricht----- > >>Von: Chris Clark [mailto:[EMAIL PROTECTED] > >>Gesendet: Mittwoch, 27. August 2003 14:13 > >>An: [EMAIL PROTECTED] > >>Betreff: RE: Empty Webapp build? > >> > >> > >>If you check the install.txt file you'll see that there is a > >>build.properties file wherein you can specify what to exclude. > >> > >>Note: depending on what version you're using, you may or may not have any > >>luck with this. (e.g. in 2.1m2 you can't exclude the deprecated package > >> > >> > >as > > > > > >>it gets used by other components you need.) > >> > >>If you just want a blank project, you can create a subdirectory under > >>webapp. The default sitemap.xmap sitting in webapp has code to automount > >>any subdirectories you create. The only "catch" is that you'll see your > >>directory name in the URL. > >> > >>e.g. http://localhost:8888/your-dir/ > >> > >>Cheers, > >>Chris > >> > >> > >> > >>>-----Original Message----- > >>>From: Robert Simmons [SMTP:[EMAIL PROTECTED] > >>>Sent: Wednesday, August 27, 2003 7:33 AM > >>>To: Cocoon Users (E-Mail) > >>>Subject: Empty Webapp build? > >>> > >>>Greetings, > >>> > >>>Is there a target that will allow me to build cocoon without the > >>>documentation or examples? I want to build a BLANK web site with the > >>> > >>> > >basic > > > > > >>>sitemap for starting a new project. > >>> > >>>-- Robert > >>> > >>>--------------------------------------------------------------------- > >>>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] > >> > >>--------------------------------------------------------------------- > >>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] > > > >--------------------------------------------------------------------- > >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]
