cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Clark" <Chris.Cl...@teranet.ca>
Subject RE: "Production" build for Cocoon?
Date Fri, 22 Aug 2003 16:20:34 GMT
Thanks.
I was just about to reply saying that the local.*.properties approach doesn't really work.
I tried excluding some things that I didn't want and the build simply failed.  
(One of the things I excluded was the "deprecated" package, but apparently Cocoon needs it
in 2.1m2.)

Also, when I excluded both the scratchpad and the samples from the webapp, some of the directories
were created before the build failed again which is not what I expected.

[As an aside, we tried doing the "build war" and then deploying the war file under Weblogic
7.0 at one point.  It didn't work and eventually we gave up and just copied over the exploded
directories.
I know we're all developers and so we can figure out how to deploy things as we want, but
at the same time, it would make Cocoon that much more attractive as a tool if some of these
things (like a "production war file") came "out of the box".]

If anyone is interested, here's the results I got when I changed the properties files...
-- Chris

Changed portion of local.build.properties:
# ---- Webapp ------------------------------------------------------------------

exclude.webapp.documentation=true
exclude.webapp.javadocs=true
exclude.webapp.idldocs=true
exclude.webapp.scratchpad=true
exclude.webapp.samples=true

# ---- Build Exclusions --------------------------------------------------------

#exclude.scratchpad=true
#exclude.deprecated=true
exclude.javadocs=true
exclude.idldocs=true

end result:
BUILD FAILED
file:C:/ELRS/cocoon-2.1m2/src/targets/samples-build.xml:71: IOException: java.io
.FileNotFoundException: C:\ELRS\cocoon-2.1m2\build\webapp\samples\samples.xml (T
he system cannot find the file specified)

Total time: 3 minutes 10 seconds

Directory tree of webapp:
C:\ELRS\cocoon-2.1m2\build\webapp>tree
Folder PATH listing
Volume serial number is 0006FE80 EC6A:AC82
C:.
????resources
?   ????icons
?   ????images
?   ????logos
?   ????scripts
?   ????styles
????samples
?   ????castor
?   ?   ????castor-mappings
?   ?   ????doc
?   ????imagereader
?   ????jxforms
?   ?   ????flow
?   ?   ????schematron
?   ?   ????stylesheets
?   ?   ????view
?   ????paginator
?   ?   ????content
?   ?   ????pagesheets
?   ?   ????stylesheets
?   ????petstore
?       ????flow
?       ????images
?       ????stylesheets
?       ????view
?           ????jexl
?           ????jxforms
?           ????jxpath
?           ????templates
?           ????xsp
????stylesheets
?   ????system
????WEB-INF
    ????classes
    ????db
    ????deli
    ?   ????config
    ?   ?   ????vocab
    ?   ????legacyProfiles
    ????entities
    ?   ????catalog-demo
    ?   ????w3c
    ????lib

> -----Original Message-----
> From:	Roger I Martin PhD [SMTP:hypernexdev@hypernexinc.com]
> Sent:	Friday, August 22, 2003 12:06 PM
> To:	dev@cocoon.apache.org
> Subject:	Re: "Production" build for Cocoon?
> 
> standalone-demo build target is one of the worst ways to work with Cocoon;
> yet alone achieve what Chris is asking.  Cocoon is a super charged super
> powerful servlet that can be used to achieve some pretty amazing results.
> 
> I've read the INSTALL.txt and it is a excellent example of unprofessional
> writing.  In fact it is simply obnoxious.
> 
> Chris,
> 
> There is no simple way to achieve what you want but the start is to think of
> the definition and requirements of the webapp concept and pull out of the
> Cocoon development complex, the pieces needed as it is used as a servlet
> inside your webapp (instead of the other way around) and any xsl you depend
> on.  You need the cocoon jars in the \build\webapp\WEB-INF\lib directory and
> you need to come up with your own usually simple ant build(Most webapps can
> be developed in place without any need for an ant script but simply back up
> frequently).  You'll need to develop a sitemap that isn't a sub sitemap of> 
> the cocoon development complex, complete a webapp\WEB-INF filled with what
> you need to configure cocoon and any other servlet or webapp component you
> may employ.  Any custom code that you add to Cocoon needs compiled of course
> and can be in another jar that you put on the classpath in front of the
> cocoon.jar.  You can save hours of your time as soon as you are free from
> the cocoon ant build script.  You can make a change, test and change again
> much more rapidly then.
> 
> For Cocoon developers: you need to start thinking of Cocoon as a servlet
> intended to be used "inside" of your customer's webapp.  If I opened an M$
> product out of the box and the way to "INSTALL" it was described as in
> INSTALL.txt with the results far from "That's it!" I would not hesitate to
> return it.
> 
> Roger
> 
> ----- Original Message ----- 
> From: "Giacomo Pati" <giacomo@apache.org>
> To: <dev@cocoon.apache.org>
> Sent: Friday, August 22, 2003 10:31 AM
> Subject: RE: "Production" build for Cocoon?
> 
> 
> > On Fri, 22 Aug 2003, Chris Clark wrote:
> >
> > > Thanks.
> > > I had read it, but I'd forgotten about the properties files as it was
> some time ago and the install.txt isn't something I generally go back and
> read after I've finishing installing something and it's working.
> >
> > Hope it helps as we followed it with good success ;-)
> >
> > Giacomo
> >
> > >
> > > > -----Original Message-----
> > > > From: Giacomo Pati [SMTP:giacomo@apache.org]
> > > > Sent: Friday, August 22, 2003 9:25 AM
> > > > To: dev@cocoon.apache.org
> > > > Subject: Re: "Production" build for Cocoon?
> > > >
> > > >
> > > > Ever read the INSTALL.txt?
> > > >
> > > >
> > > > On Fri, 22 Aug 2003, Chris Clark wrote:
> > > >
> > > > > Just wondering if there's any easy way of making a "Production"
> build
> > > > > of Cocoon.  The default build compiles all of the samples and makes
> > > > > them available which is fine for development.  However, when we
> > > > > eventually go "live", we'd like to be able to deploy a minimal build
> > > > > that doesn't have the samples or javadoc, etc.
> > > > >
> > > > > We took a quick stab once at trying to remove the samples after
> doing
> > > > > the full, default build but started running into various
> > > > > file-not-found problems as the master sitemap tried to load various
> > > > > sample-related items.
> > > > >
> > > > > We're okay with using the master Cocoon sitemap (saves us a lot of
> > > > > declaring and configuring) and letting it mount our stuff, but we'd
> > > > > like to be able to do a build that leaves out all of the samples,
> etc.
> > > > >
> > > > > Is this possible?  Is it already there or are there some
> > > > > straightforward instructions on what to delete from the full build
> and
> > > > > still have things work?
> > > > >
> > > > > Thanks,
> > > > > Chris
> > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Giacomo Pati
> > > > Otego AG, Switzerland - http://www.otego.com
> > > > Orixo, the XML business alliance - http://www.orixo.com
> > > >
> > >
> > >
> > >
> >
> > --
> > Giacomo Pati
> > Otego AG, Switzerland - http://www.otego.com
> > Orixo, the XML business alliance - http://www.orixo.com
> >
> 
> 

Mime
View raw message