Re: Barracuda update (please read)....

small update.  I made some changes to how the contrib apps find their jars 
for compilation.  Here is the log message for the commit....


Per suggestion by Stefan Armbruster, I updated the contrib apps to copy all 
xmlc related jars into build/WEB-INF/lib in each respective webapp.  This 
negates the necessity of copying all the xmlc related jars to 
CATALINA_HOME/shared/lib.

         Note: The one necessity this change doesn't remove is moving 
xerces-1.4.4-xmlc-2.1.jar to either shared/lib or common/endorsed.  This is 
because of the Sun classloading spec and the servlet spec which state that 
you cannot put endorsed libraries ( org.xml.*, javax.xml.*, and 
org.w3c.dom.*) under WEB-INF/lib.

         I also am now pointing to the servlet-2.3.jar in Barracuda's 
WEB-INF/jars directory for compilation.  This means there are no more 
dependencies on Tomcat existing on your system to build the contrib 
apps.  However, the point of them is to run them and the catalina-* targets 
will not work if you don't have Tomcat installed.


So, in the instructions below, you can ignore steps "b" and "c" and the 
contrib apps will build without the presence of Tomcat.  However, if you 
want to run catalina-install and run the apps under Tomcat, you will have 
to copy xerces-1.4.4-xmlc-2.1.jar to either shared/lib or 
common/endorsed.  shared/lib is the least intrusive and doesn't necessitate 
deleting xerces jars in common/endorsed.  However, XMLC compiled XML file 
(as opposed to HTML files) will fail to load unless you have 
xerces-1.4.4-xmlc-2.1.jar in common/endorsed and remove pre-existing xerces 
jars (xercesImpl.jar and xmlParserAPIs.jar).

Additionally, and I forgot to mention this before, make sure you add a user 
with the role of "manager" to tomcat-users.xml and then make sure that one 
of your build.properties files contains that info.  You can do the latter 
easily without modifying anything under the Barracuda tree.  Just create 
the following file in ${user.home} on your system....

.build.properties   (notice the period at the beginning of the file name!)

Add something like the following to that file...

manager.username=manager
manager.password=simpsons

The username and password should match that of the user given the role of 
"manager" that you set up in tomcat-users.xml.

That properties file will be read before any of the properties files in 
Barracuda which allows you to override properties.  I use this to put 
control compiler options as well.

Note you can also have:

.BarracudaMVC-build.properties
.contrib-dbroggish-build.properties
.contrib-sam-build.properties

These files, if they exist, are loaded even before .build.properties so you 
can override properties specifically and preferentially per-project.  For 
Windows users, you will have to create these files via the command line 
because the windows gui wont' allow you to create files that start with a 
period (lame).  This is accomplished by the following in each build.xml 
file....

     <property file="${user.home}/.${ant.project.name}-build.properties"/>
     <property file="${user.home}/.build.properties"/>


Any questions, let me know.

Jake


At 12:37 AM 2/18/2003 -0600, you wrote:

>Hi everyone,
>
>I updated Barracuda with a couple things (and tagged it with CVS tag 
>jrk_20030217).
>
>1.  New logging package from log4-sandbox.  This is, pretty much, the same 
>functional code that was in the barracuda-log4j.jar and 
>barracuda-webapp.jar.  The equivalents are now 
>log4j-sandbox-selector-0.1alpha.jar and 
>log4j-sandbox-servlet-0.1alpha.jar.  Again, the former goes wherever 
>log4j.jar goes and the latter goes in WEB-INF/lib of your webapp.
>
>The new configuration for your context listener looks like:
>
>            <listener>
>                 <listener-class>
>                 org.apache.log4j.servlet.InitContextListener
>                 </listener-class>
>         </listener>
>
>See Barracuda's sample.web.xml or any of the contrib app sample.web.xml files.
>
>
>2.  I added Stefan Armbruster's new contrib app.  It uses some of Diez' 
>contrib stuff along with new useful code that Stefan has provided.  This 
>is yet another example of how to code with Barracuda and looks to be a 
>pretty good one :-)  Check it out!
>
>In order to install the contrib apps, make sure of the following....
>
>a.  You have a recent install of Tomcat-4.1.x
>b.  You have added the following jars to CATALINA_HOME/shared/lib
>         cos.jar
>         gnu-regexp-1.1.4.jar
>         jtidy-r7-xmlc-2.1.jar
>         log4j-sandbox-selector-0.1alpha.jar
>         wireless-xmlc-2.1.jar
>         xerces-1.4.4-xmlc-2.1.jar  (this could also be in common/endorsed 
> in place of existing xerces jars....your choice)
>         xhtml-xmlc-2.1.jar
>         xmlc-2.1.jar
>c.  You have added the following jars to CATALINA_HOME/common/lib
>         log4j-1.2.7.jar  (copy log4j-1.2.7a.jar from 
> Barracuda/WEB-INF/lib to common/lib/log4j-1.2.7.jar)
>
>Now start Tomcat and run the following on the command line from 
>Barracuda/src...
>
>ant contrib -Dsubproject=all -Dsubtarget=catalina-install
>
>That will build Barracuda, build the core contrib stuff, and build and 
>install each contrib app to Tomcat all in one-fell-swoop!
>
>You could just type "ant contrib" and then the build will prompt your for 
>the above values.  To install any one contrib app, just name it.  That is, 
>instead of "all", use "dbroggisch" or "sam".
>
>
>One other thing of note is that I updated my modified version of Diez' 
>contrib app on my ftp to match up with the CVS source tag with 
>jrk_20030217.  Might want to grab this update if you are using it for an 
>example Barracuda build.
>ftp://ftp.visi.com/users/hoju/pub/
>or
>ftp://ftp.visi.com/users/hoju/pub/barracuda-pages.sample_2003-02-17.zip
>
>
>Have fun!
>
>Any questions or problems, let me know.
>
>Jake
>
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda