Re: Examples not working
Denny Chambers <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
All seem to work now except for this one: http://www.barracudamvc.org/Barracuda/tutorial/HelloWorld3 Christian Cryder wrote: >This should be doubly fixed now. > >We had forgotten to install the common XMLC/Xalan libraries in Tomcat's >shared/lib. That's done now, so any webapps that run on this machine will >have access to these libraries. > >In addition, I modified the Barracuda install target so that in addition to >copying needed files from lib-cvs to lib, it also copies the xmlc/xalan >stuff from jars to lib. What this means is that Barracuda truly should run >out of the box on a Tomcat (or other appserver) - simply > >a) update from cvs >b) run the ant install target (to get the appropriate jar files in the right >place) >c) install the webapp in the appserver > >This gives us the advantage of being able to test new versions of Barracuda >libraries locally within the Barracuda webapp, and then only upgrading them >across the entire server when we're ready. At that point, all we have to do >is copy them into the tomcat shared/lib dir. > >Hope that helps! >Christian > >---------------------------------------------- >Christian Cryder [[email protected]] >Internet Architect, ATMReports.com >Barracuda - http://barracuda.enhydra.org >---------------------------------------------- >"Coffee? I could quit anytime, just not today" > > > >>-----Original Message----- >>From: [email protected] >>[mailto:[email protected]]On Behalf Of Christian Cryder >>Sent: Thursday, January 16, 2003 3:02 PM >>To: [email protected] >>Subject: RE: [Barracuda] Examples not working >> >> >> >> >>>This is good to know. I also have noticed that none of the tutorials are >>>working. Is this something that still needs work? >>> >>> >>Yeah...they are working locally, and _should_ be working on >>bmvc.org, but I >>just verified that they're not...my guess is that they are not being >>included in one of the jars. I'll check into it... >> >>Christian >>---------------------------------------------- >>Christian Cryder [[email protected]] >>Internet Architect, ATMReports.com >>Barracuda - http://barracuda.enhydra.org >>---------------------------------------------- >>"Coffee? I could quit anytime, just not today" >> >> >> >>>-----Original Message----- >>>From: [email protected] >>>[mailto:[email protected]]On Behalf Of Denny Chambers >>>Sent: Thursday, January 16, 2003 2:55 PM >>>To: [email protected] >>>Subject: Re: [Barracuda] Contrib structure >>> >>> >>>This is good to know. I also have noticed that none of the tutorials are >>>working. Is this something that still needs work? >>> >>>Christian Cryder wrote: >>> >>> >>> >>>>>module). I would also like to recommend making the >>>>> >>>>> >>barracudamvc.org web >> >> >>>>>pages a seperate module, since that would allow you to assign >>>>> >>>>> >>access to >> >> >>>>>folks, who want to work on the web site, documention, or demos. Just a >>>>>suggestion. >>>>> >>>>> >>>>> >>>>> >>>>Well, we will keep them as part of the Barracuda docs, but we >>>> >>>> >>can control >> >> >>>>cvs access to just this portion of the tree - Shawn and I >>>> >>>> >>discussed this >> >> >>>>already - basically we will be able to give people commit access >>>> >>>> >>>to the docs >>> >>> >>>>portion without actually giving them commit privileges to the >>>> >>>> >>>src trees... >>> >>> >>>>Christian >>>> >>>>---------------------------------------------- >>>>Christian Cryder [[email protected]] >>>>Internet Architect, ATMReports.com >>>>Barracuda - http://barracuda.enhydra.org >>>>---------------------------------------------- >>>>"Coffee? I could quit anytime, just not today" >>>> >>>> >>>> >>>> >>>> >>>>>-----Original Message----- >>>>>From: [email protected] >>>>>[mailto:[email protected]]On Behalf Of Denny Chambers >>>>>Sent: Thursday, January 16, 2003 1:17 PM >>>>>To: [email protected] >>>>>Subject: Re: [Barracuda] Contrib structure >>>>> >>>>> >>>>>I like this approach better. My first thought was to see if >>>>> >>>>> >>contributors >> >> >>>>>could get their own account on the server. Then we could setup >>>>>apache/tomcat to allow user directories (like >>>>>www.barracudamvc.org/~dennyc - i believe this possible with tomcat). >>>>>This way each contributor would be able to set up there own web space >>>>>(Web apps, docs, source, binaries) under there user directory. My >>>>>preference would be to keep contrib stuff seperate from the Barracuda >>>>>CVS module. So my vote is to keep the contrib stuff totally >>>>> >>>>> >>seperate, so >> >> >>>>>that users can download the contrib code totally seperate from the CVS >>>>>(from each contrib user personal directory as a zip file), or that the >>>>>contrib stuff becomes a seperate module in CVS. By atleast making it a >>>>>seperate module, it will allow you to do finer grain access control to >>>>>cvs (developer can have access to contrib module, but not the >>>>> >>>>> >>Barracuda >> >> >>>>>module). I would also like to recommend making the >>>>> >>>>> >>barracudamvc.org web >> >> >>>>>pages a seperate module, since that would allow you to assign >>>>> >>>>> >>access to >> >> >>>>>folks, who want to work on the web site, documention, or demos. Just a >>>>>suggestion. >>>>> >>>>>Denny >>>>> >>>>>Christian Cryder wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>Hi folks, >>>>>> >>>>>>I'd like to take this opportunity to start a conversation on >>>>>> >>>>>> >>>how best to >>> >>> >>>>>>structure the contrib stuff on the new server. Basically, what >>>>>> >>>>>> >>>>>> >>>>>> >>>>>we have right >>>>> >>>>> >>>>> >>>>> >>>>>>now is something like this: >>>>>> >>>>>>/Barracuda >>>>>>/src >>>>>> /org/enhydra/barracuda... >>>>>> ... >>>>>> /core (core packages) >>>>>> /contrib >>>>>> /dbroggisch >>>>>> /display (source) >>>>>> /dtd >>>>>> /repopulation (source) >>>>>> /webapp >>>>>> /docs >>>>>> /src >>>>>> /src_mockups >>>>>> /web >>>>>> /WEB-INF >>>>>> ... (other contributors) >>>>>>/WEB-INF >>>>>> /lib-cvs (this is where the jars are kept) >>>>>> >>>>>>Right now, when you build the contrib package, the classes get >>>>>> >>>>>> >>>>>> >>>>>> >>>>>compiled into >>>>> >>>>> >>>>> >>>>> >>>>>>the main Barracuda /WEB-INF/classes directory, and are then >>>>>> >>>>>> >>eventually >> >> >>>>>>jarred into the main WEB-INF/lib-cvs/barracuda-contrib.jar. I'd >>>>>> >>>>>> >>>>>> >>>>>> >>>>>like to keep >>>>> >>>>> >>>>> >>>>> >>>>>>this working this way, since it keeps all the actual source >>>>>> >>>>>> >>>>>> >>>>>> >>>>>attached to the >>>>> >>>>> >>>>> >>>>> >>>>>>main Barracuda project. >>>>>> >>>>>>Now, where things get murky (IMO), is that the way things >>>>>> >>>>>> >>are currently >> >> >>>>>>structure, Diez's contrib structure also contains a sample >>>>>> >>>>>> >>>webapps, with >>> >>> >>>>>>docs, etc. This is the part I find confusing, since its >>>>>> >>>>>> >>>ultimately rooted >>> >>> >>>>>>under Barracuda's /src directory (and its really not source at all). >>>>>> >>>>>>SO...what I'd like to propose is that we structure our cvs tree >>>>>> >>>>>> >>>>>> >>>>>> >>>>>like this: >>>>> >>>>> >>>>> >>>>> >>>>>>/var/cvs... >>>>>> /Barracuda >>>>>> /BarracudaDiskRack >>>>>> /Contrib >>>>>> /dbroggisch (webapp) >>>>>> /docs >>>>>> /WEB-INF >>>>>> /christianc (webapp) >>>>>> /docs >>>>>> /WEB-INF >>>>>> /hoju >>>>>> /Sample1 (webapp) >>>>>> /docs >>>>>> /WEB-INF >>>>>> /Sample2 (webapp) >>>>>> /docs >>>>>> /WEB-INF >>>>>> >>>>>>The basic idea here is that >>>>>> >>>>>>a) anyone can get their own contrib directory under the >>>>>> >>>>>> >>>>>> >>>>>> >>>>>Barracuda tree...add >>>>> >>>>> >>>>> >>>>> >>>>>>your code there, and it'll get automatically included into the >>>>>>barracuda-contrib.jar >>>>>> >>>>>>b) anyone who wants to set up sample webapps that demonstrate >>>>>> >>>>>> >>>>>> >>>>>> >>>>>their code can >>>>> >>>>> >>>>> >>>>> >>>>>>then get their own contrib directory under the Contrib cvs >>>>>> >>>>>> >>>>>> >>>>>> >>>>>tree...they could >>>>> >>>>> >>>>> >>>>> >>>>>>have one webapp or many; its totally up to them. They could also use >>>>>>whatever build system or format they want. >>>>>> >>>>>>I think this would give us maximum flexiblity to experiement >>>>>> >>>>>> >>>with various >>> >>> >>>>>>approaches, while keeping the overall Barracuda src tree >>>>>> >>>>>> >>>>>> >>>>>> >>>>>relatively clean. >>>>> >>>>> >>>>> >>>>> >>>>>>One of the keys to making this work would be to adopt Jakes >>>>>> >>>>>> >>>>>> >>>>>> >>>>>ccf.xml method >>>>> >>>>> >>>>> >>>>> >>>>>>for installing webapps into tomcat...then, every app (including >>>>>> >>>>>> >>>>>> >>>>>> >>>>>Barracuda) >>>>> >>>>> >>>>> >>>>> >>>>>>could register with Tomcat without us having to constantly edit the >>>>>>server.xml file. >>>>>> >>>>>>These are just my initial thoughts...comments and feedback welcome! >>>>>> >>>>>>Christian >>>>>>---------------------------------------------- >>>>>>Christian Cryder [[email protected]] >>>>>>Internet Architect, ATMReports.com >>>>>>Barracuda - http://barracuda.enhydra.org >>>>>>---------------------------------------------- >>>>>>"Coffee? I could quit anytime, just not today" >>>>>> >>>>>>_______________________________________________ >>>>>>Barracuda mailing list >>>>>>[email protected] >>>>>>http://barracudamvc.org/lists/listinfo/barracuda >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>_______________________________________________ >>>>>Barracuda mailing list >>>>>[email protected] >>>>>http://barracudamvc.org/lists/listinfo/barracuda >>>>> >>>>> >>>>> >>>>> >>>>_______________________________________________ >>>>Barracuda mailing list >>>>[email protected] >>>>http://barracudamvc.org/lists/listinfo/barracuda >>>> >>>> >>>> >>>> >>>> >>>> >>>_______________________________________________ >>>Barracuda mailing list >>>[email protected] >>>http://barracudamvc.org/lists/listinfo/barracuda >>> >>> >>_______________________________________________ >>Barracuda mailing list >>[email protected] >>http://barracudamvc.org/lists/listinfo/barracuda >> >> > >_______________________________________________ >Barracuda mailing list >[email protected] >http://barracudamvc.org/lists/listinfo/barracuda > > > >