Re: [Babeldoc-devel] Babeldoc development

[Dejan K. <dej...@nb...>]

I have tagged all sources in CVS with tag V-1-0-RC1.

Dejan


----- Original Message -----
From: "Bruce McDonald" <br...@mc...>
To: "Dejan Krsmanovic" <dej...@nb...>
Cc: "Babeldoc Developers List" <bab...@li...>
Sent: Friday, February 28, 2003 11:36 PM
Subject: Re: [Babeldoc-devel] Babeldoc development


> Dejan, All:
>
> I am about to make the first release of the RC1 codebase.  This code
> is now completely restructured and is ready for the public.  The finishing
> touches will include crypto and j2ee support and I dont know about the
> j2ee.  The last significant hurdle breached today was how babeldoc finds
> its modules when running in a web container.  I introduced a system
> property that tells babeldoc module handling code to scan one or more
> directories for candidate files.  This sounds like a major hack but its
> actuall quite subtle.  Heres the deal:
>
> a Servlet in Tomcat/catalina needs to have all of its libraries in the
> ./shared/lib or in the webapp/<war>/WEB-INF/lib directory.  Now, I opted
> to put all the code in shared lib to avoid very bloated war files  and to
> encourage code sharing.  The catalina script to start the web container
> gets started with the environment variable JAVA_OPTS which has the sytem
> property of the directory to scan, which is the shared lib.  As babeldoc
> starts, it scans this directory and finds all the modules.  There is NO
> other way for 3rd party modules to get stuff into the classpath (the
> catalina script disregards the CLASSPATH).
>
> How do we automate the copying over of the libs and the wars to the
> catalina directory.  This is handled by a script which is copied from the
> web/bin directory to the build/bin directory.  It has a number of tokens
> (of the form @token-name@) which get filled in by the build scripts when
> the copy is performed.  The values for the tokens come from the
> modules/web/build.properties file but can be overriden in a top-level
> file, called locals.properties.  These properties tell the script where to
> find catalina, the location of the shared directory and the actual name of
> the script to start catalina.
>
> so to build and deploy the babeldoc web stuff do this:
>
> c:\babeldoc>build
> c:\babeldoc>build\bin\catalina start
>
> this assumes that catalina is in a directory:
> \babeldoc\..\tomcat.v4.1
>
> fair enough.
>
> Bruce.
>
>
> On Fri, 28 Feb 2003, Dejan Krsmanovic wrote:
>
> > Hi Bruce!
> >
> > How new Babeldoc is going? Currently I have not much time for working on
it,
> > but as soon as I have time I will add crypto module to new Babeldoc
> > stucture....
> >
> > Have a nice weekend,
> > Dejan
> >
> > p.s. Have you looked at mail archives on SF for this list? There are a
lot
> > of doubled or even tripled messages! There were also  3 messages from
1969
> > year ;)
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
>
> --
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel