Re[2]: Examples not working
Jacob Kjome <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Organization | Springfield Nuclear Plant |
| Message-ID | <[email protected]> |
Hello Christian, Like I said in another email, the cleanest thing to do is to put the jars in shared/lib so that it doesn't affect any Tomcat internals. However, things will probably work just fine in common/endorsed so it is probably fine to leave things that way. Jake Friday, January 17, 2003, 10:44:20 AM, you wrote: CC> Ok, so with xalan and xerces OUT of my Barracuda's WEB-INF/lib, I still get CC> the error on HelloWorld3. Now, these jars ARE installed in Tomcat's CC> shared/lib. CC> So, I moved these to Tomcat's endorsed directory, and voila! everything CC> works again! CC> Ok, very cool...I will upgrade accordingly on the server and check it out up CC> there as well. We probably need to come up with a nice, clean install doc CC> that explains exactly what to put where...I'll try and do that this weekend. CC> Thanks for your help on this! CC> Christian CC> ---------------------------------------------- CC> Christian Cryder [[email protected]] CC> Internet Architect, ATMReports.com CC> Barracuda - http://barracudamvc.org CC> ---------------------------------------------- CC> "Coffee? I could quit anytime, just not today" CC> -----Original Message----- CC> From: [email protected] CC> [mailto:[email protected]]On Behalf Of Jacob Kjome CC> Sent: Thursday, January 16, 2003 10:38 PM CC> To: [email protected] CC> Subject: RE: [Barracuda] Examples not working CC> Hmm.... one thing I stated in my previous email about Xerces and Xalan was CC> that "Currently, by some luck and some super coding from Richard Kunze, we CC> are able to put our version of Xerces in shared/lib even while Xerces2 is in CC> common/endorsed". Well, as it turns out, this seems true in every case CC> except the one dealing with the XMLC templates compiled from XML files CC> rather than HTML files. CC> The fix is quite simple. Remove xercesImpl.jar and xmlParserAPIs.jar from CC> CATALINA_HOME/common/endorsed. It will work perfectly, I promise. Or, you CC> can always use the JDK1.4-lite version of Tomcat. However, that excludes CC> more libs than just the xml parser and I'd suggest using the full version CC> and deleting the jars as stated previously. CC> Now, I know that this was a problem even with XMLC compiled HTML files at CC> one point before Richard Kunze made some modifcations to allow xerces to be CC> in shared/lib even when Xerces2 was in common/endorsed. I just can't CC> remember what those mods were? CC> Richard, if you are reading this, could you expound on what you did to CC> make the latter case work? Can the same be done for the case of XMLC CC> compiled XML templates? Hopefully you remember the change you made (and the CC> conversation we had about it). CC> The other stuff about not putting xerces and xalan (or any of the xmlc CC> classes, IMO) in WEB-INF/lib is still completely valid and has little to do CC> with this issue. The should be in shared/lib and nowhere else. CC> Jake CC> At 04:38 PM 1/16/2003 -0700, you wrote: CC> Hmmm...here's some more detail: CC> ----- Root Cause ----- CC> java.lang.IllegalAccessError: tried to access method CC> org.apache.xerces.dom.DocumentTypeImpl.setOwnerDocument(Lorg/apache/xerces/d CC> om/CoreDocumentImpl;)V from class CC> org.enhydra.xml.lazydom.LazyDocumentType CC> at CC> org.enhydra.xml.lazydom.LazyDocumentType.setOwnerDocument(LazyDocumentType.j CC> ava:74) CC> at CC> org.enhydra.xml.lazydom.LazyDocument.<init>(LazyDocument.java:123) CC> at CC> org.enhydra.xml.xmlc.dom.lazydom.LazyDomFactory.createDocument(LazyDomFactor CC> y.java:94) CC> at CC> org.enhydra.barracuda.tutorials.xmlc.HelloWorld3XML.buildTemplateSubDocument CC> (Unknown Source) CC> at CC> org.enhydra.barracuda.tutorials.xmlc.HelloWorld3XML.<clinit>(Unknown CC> Source) CC> at java.lang.Class.forName0(Native Method) CC> at java.lang.Class.forName(Class.java:140) CC> at CC> org.enhydra.barracuda.tutorials.comp.HelloWorld3.class$(HelloWorld3.java:64) CC> at CC> org.enhydra.barracuda.tutorials.comp.HelloWorld3.handleDefault(HelloWorld3.j CC> ava:64) CC> at CC> org.enhydra.barracuda.core.comp.helper.ComponentGateway.handleDefault(Compon CC> entGateway.java:261) CC> at CC> org.enhydra.barracuda.core.comp.helper.ComponentGateway.doGet(ComponentGatew CC> ay.java:170) CC> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) CC> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) CC> Looks to me like there is something in the current version of XMLC (2.1) CC> which is choking on the XML doc types. Its possible that this was CC> introduced CC> in the last version of XMLC and just not caught until now...Jake - CC> you've CC> spent some time looking at the internals of XMLC; any thoughts here? CC> I'll look at htis more later once I get a bit of time... CC> Christian CC> ---------------------------------------------- CC> Christian Cryder [[email protected]] CC> Internet Architect, ATMReports.com CC> Barracuda - http://barracuda.enhydra.org CC> ---------------------------------------------- CC> "Coffee? I could quit anytime, just not today" CC> > -----Original Message----- CC> > From: [email protected] CC> > [mailto:[email protected]]On Behalf Of Christian Cryder CC> > Sent: Thursday, January 16, 2003 4:21 PM CC> > To: [email protected] CC> > Subject: RE: [Barracuda] Examples not working CC> > CC> > CC> > Wierd...I'm getting that same error here locally too...I'll have CC> > to look at CC> > this more closely...maybe tonight. Seems to be dying on this line CC> right CC> > here: CC> > CC> > Class pageCl = HelloWorld3XML.class; CC> > CC> > But that class is clearly sitting there in the classpath. Hmmm.... CC> > CC> > Christian CC> > ---------------------------------------------- CC> > Christian Cryder [[email protected]] CC> > Internet Architect, ATMReports.com CC> > Barracuda - http://barracuda.enhydra.org CC> > ---------------------------------------------- CC> > "Coffee? I could quit anytime, just not today" CC> > CC> > > -----Original Message----- CC> > > From: [email protected] CC> > > [mailto:[email protected]]On Behalf Of Denny Chambers CC> > > Sent: Thursday, January 16, 2003 3:52 PM CC> > > To: [email protected] CC> > > Subject: Re: [Barracuda] Examples not working CC> > > CC> > > CC> > > All seem to work now except for this one: CC> > > CC> > > http://www.barracudamvc.org/Barracuda/tutorial/HelloWorld3 CC> > > CC> > > CC> > > Christian Cryder wrote: CC> > > CC> > > >This should be doubly fixed now. CC> > > > CC> > > >We had forgotten to install the common XMLC/Xalan libraries in CC> Tomcat's CC> > > >shared/lib. That's done now, so any webapps that run on this CC> > machine will CC> > > >have access to these libraries. CC> > > > CC> > > >In addition, I modified the Barracuda install target so that in CC> > > addition to CC> > > >copying needed files from lib-cvs to lib, it also copies the CC> xmlc/xalan CC> > > >stuff from jars to lib. What this means is that Barracuda truly CC> > > should run CC> > > >out of the box on a Tomcat (or other appserver) - simply CC> > > > CC> > > >a) update from cvs CC> > > >b) run the ant install target (to get the appropriate jar files CC> > > in the right CC> > > >place) CC> > > >c) install the webapp in the appserver CC> > > > CC> > > >This gives us the advantage of being able to test new versions CC> > > of Barracuda CC> > > >libraries locally within the Barracuda webapp, and then only CC> > > upgrading them CC> > > >across the entire server when we're ready. At that point, all we CC> > > have to do CC> > > >is copy them into the tomcat shared/lib dir. CC> > > > CC> > > >Hope that helps! CC> > > >Christian CC> > > > CC> > > >---------------------------------------------- CC> > > >Christian Cryder [[email protected]] CC> > > >Internet Architect, ATMReports.com CC> > > >Barracuda - http://barracuda.enhydra.org CC> > > >---------------------------------------------- CC> > > >"Coffee? I could quit anytime, just not today" CC> > > > CC> > > > CC> > > > CC> > > >>-----Original Message----- CC> > > >>From: [email protected] CC> > > >>[mailto:[email protected]]On Behalf Of Christian CC> Cryder CC> > > >>Sent: Thursday, January 16, 2003 3:02 PM CC> > > >>To: [email protected] CC> > > >>Subject: RE: [Barracuda] Examples not working CC> > > >> CC> > > >> CC> > > >> CC> > > >> CC> > > >>>This is good to know. I also have noticed that none of the CC> > > tutorials are CC> > > >>>working. Is this something that still needs work? CC> > > >>> CC> > > >>> CC> > > >>Yeah...they are working locally, and _should_ be working on CC> > > >>bmvc.org, but I CC> > > >>just verified that they're not...my guess is that they are not CC> being CC> > > >>included in one of the jars. I'll check into it... CC> > > >> CC> > > >>Christian CC> > > >>---------------------------------------------- CC> > > >>Christian Cryder [[email protected]] CC> > > >>Internet Architect, ATMReports.com CC> > > >>Barracuda - http://barracuda.enhydra.org CC> > > >>---------------------------------------------- CC> > > >>"Coffee? I could quit anytime, just not today" CC> > > >> CC> > > >> CC> > > >> CC> > > >>>-----Original Message----- CC> > > >>>From: [email protected] CC> > > >>>[mailto:[email protected]]On Behalf Of Denny CC> Chambers CC> > > >>>Sent: Thursday, January 16, 2003 2:55 PM CC> > > >>>To: [email protected] CC> > > >>>Subject: Re: [Barracuda] Contrib structure CC> > > >>> CC> > > >>> CC> > > >>>This is good to know. I also have noticed that none of the CC> > > tutorials are CC> > > >>>working. Is this something that still needs work? CC> > > >>> CC> > > >>>Christian Cryder wrote: CC> > > >>> CC> > > >>> CC> > > >>> CC> > > >>>>>module). I would also like to recommend making the CC> > > >>>>> CC> > > >>>>> CC> > > >>barracudamvc.org web CC> > > >> CC> > > >> CC> > > >>>>>pages a seperate module, since that would allow you to assign CC> > > >>>>> CC> > > >>>>> CC> > > >>access to CC> > > >> CC> > > >> CC> > > >>>>>folks, who want to work on the web site, documention, or CC> > > demos. Just a CC> > > >>>>>suggestion. CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>Well, we will keep them as part of the Barracuda docs, but we CC> > > >>>> CC> > > >>>> CC> > > >>can control CC> > > >> CC> > > >> CC> > > >>>>cvs access to just this portion of the tree - Shawn and I CC> > > >>>> CC> > > >>>> CC> > > >>discussed this CC> > > >> CC> > > >> CC> > > >>>>already - basically we will be able to give people commit access CC> > > >>>> CC> > > >>>> CC> > > >>>to the docs CC> > > >>> CC> > > >>> CC> > > >>>>portion without actually giving them commit privileges to the CC> > > >>>> CC> > > >>>> CC> > > >>>src trees... CC> > > >>> CC> > > >>> CC> > > >>>>Christian CC> > > >>>> CC> > > >>>>---------------------------------------------- CC> > > >>>>Christian Cryder [[email protected]] CC> > > >>>>Internet Architect, ATMReports.com CC> > > >>>>Barracuda - http://barracuda.enhydra.org CC> > > >>>>---------------------------------------------- CC> > > >>>>"Coffee? I could quit anytime, just not today" CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>>>-----Original Message----- CC> > > >>>>>From: [email protected] CC> > > >>>>>[mailto:[email protected]]On Behalf Of CC> > Denny Chambers CC> > > >>>>>Sent: Thursday, January 16, 2003 1:17 PM CC> > > >>>>>To: [email protected] CC> > > >>>>>Subject: Re: [Barracuda] Contrib structure CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>I like this approach better. My first thought was to see if CC> > > >>>>> CC> > > >>>>> CC> > > >>contributors CC> > > >> CC> > > >> CC> > > >>>>>could get their own account on the server. Then we could setup CC> > > >>>>>apache/tomcat to allow user directories (like CC> > > >>>>>www.barracudamvc.org/~dennyc - i believe this possible CC> > with tomcat). CC> > > >>>>>This way each contributor would be able to set up there CC> > own web space CC> > > >>>>>(Web apps, docs, source, binaries) under there user directory. CC> My CC> > > >>>>>preference would be to keep contrib stuff seperate from CC> > the Barracuda CC> > > >>>>>CVS module. So my vote is to keep the contrib stuff totally CC> > > >>>>> CC> > > >>>>> CC> > > >>seperate, so CC> > > >> CC> > > >> CC> > > >>>>>that users can download the contrib code totally seperate CC> > > from the CVS CC> > > >>>>>(from each contrib user personal directory as a zip file), CC> > > or that the CC> > > >>>>>contrib stuff becomes a seperate module in CVS. By atleast CC> > > making it a CC> > > >>>>>seperate module, it will allow you to do finer grain access CC> > > control to CC> > > >>>>>cvs (developer can have access to contrib module, but not the CC> > > >>>>> CC> > > >>>>> CC> > > >>Barracuda CC> > > >> CC> > > >> CC> > > >>>>>module). I would also like to recommend making the CC> > > >>>>> CC> > > >>>>> CC> > > >>barracudamvc.org web CC> > > >> CC> > > >> CC> > > >>>>>pages a seperate module, since that would allow you to assign CC> > > >>>>> CC> > > >>>>> CC> > > >>access to CC> > > >> CC> > > >> CC> > > >>>>>folks, who want to work on the web site, documention, or CC> > > demos. Just a CC> > > >>>>>suggestion. CC> > > >>>>> CC> > > >>>>>Denny CC> > > >>>>> CC> > > >>>>>Christian Cryder wrote: CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>Hi folks, CC> > > >>>>>> CC> > > >>>>>>I'd like to take this opportunity to start a conversation on CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>how best to CC> > > >>> CC> > > >>> CC> > > >>>>>>structure the contrib stuff on the new server. Basically, what CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>we have right CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>now is something like this: CC> > > >>>>>> CC> > > >>>>>>/Barracuda CC> > > >>>>>>/src CC> > > >>>>>> /org/enhydra/barracuda... CC> > > >>>>>> ... CC> > > >>>>>> /core (core packages) CC> > > >>>>>> /contrib CC> > > >>>>>> /dbroggisch CC> > > >>>>>> /display (source) CC> > > >>>>>> /dtd CC> > > >>>>>> /repopulation (source) CC> > > >>>>>> /webapp CC> > > >>>>>> /docs CC> > > >>>>>> /src CC> > > >>>>>> /src_mockups CC> > > >>>>>> /web CC> > > >>>>>> /WEB-INF CC> > > >>>>>> ... (other contributors) CC> > > >>>>>>/WEB-INF CC> > > >>>>>> /lib-cvs (this is where the jars are kept) CC> > > >>>>>> CC> > > >>>>>>Right now, when you build the contrib package, the classes get CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>compiled into CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>the main Barracuda /WEB-INF/classes directory, and are then CC> > > >>>>>> CC> > > >>>>>> CC> > > >>eventually CC> > > >> CC> > > >> CC> > > >>>>>>jarred into the main WEB-INF/lib-cvs/barracuda-contrib.jar. CC> I'd CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>like to keep CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>this working this way, since it keeps all the actual source CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>attached to the CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>main Barracuda project. CC> > > >>>>>> CC> > > >>>>>>Now, where things get murky (IMO), is that the way things CC> > > >>>>>> CC> > > >>>>>> CC> > > >>are currently CC> > > >> CC> > > >> CC> > > >>>>>>structure, Diez's contrib structure also contains a sample CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>webapps, with CC> > > >>> CC> > > >>> CC> > > >>>>>>docs, etc. This is the part I find confusing, since its CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>ultimately rooted CC> > > >>> CC> > > >>> CC> > > >>>>>>under Barracuda's /src directory (and its really not CC> > source at all). CC> > > >>>>>> CC> > > >>>>>>SO...what I'd like to propose is that we structure our cvs CC> tree CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>like this: CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>/var/cvs... CC> > > >>>>>> /Barracuda CC> > > >>>>>> /BarracudaDiskRack CC> > > >>>>>> /Contrib CC> > > >>>>>> /dbroggisch (webapp) CC> > > >>>>>> /docs CC> > > >>>>>> /WEB-INF CC> > > >>>>>> /christianc (webapp) CC> > > >>>>>> /docs CC> > > >>>>>> /WEB-INF CC> > > >>>>>> /hoju CC> > > >>>>>> /Sample1 (webapp) CC> > > >>>>>> /docs CC> > > >>>>>> /WEB-INF CC> > > >>>>>> /Sample2 (webapp) CC> > > >>>>>> /docs CC> > > >>>>>> /WEB-INF CC> > > >>>>>> CC> > > >>>>>>The basic idea here is that CC> > > >>>>>> CC> > > >>>>>>a) anyone can get their own contrib directory under the CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>Barracuda tree...add CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>your code there, and it'll get automatically included into the CC> > > >>>>>>barracuda-contrib.jar CC> > > >>>>>> CC> > > >>>>>>b) anyone who wants to set up sample webapps that demonstrate CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>their code can CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>then get their own contrib directory under the Contrib cvs CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>tree...they could CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>have one webapp or many; its totally up to them. They CC> > could also use CC> > > >>>>>>whatever build system or format they want. CC> > > >>>>>> CC> > > >>>>>>I think this would give us maximum flexiblity to experiement CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>with various CC> > > >>> CC> > > >>> CC> > > >>>>>>approaches, while keeping the overall Barracuda src tree CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>relatively clean. CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>One of the keys to making this work would be to adopt Jakes CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>ccf.xml method CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>for installing webapps into tomcat...then, every app CC> (including CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>Barracuda) CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>>>could register with Tomcat without us having to CC> > constantly edit the CC> > > >>>>>>server.xml file. CC> > > >>>>>> CC> > > >>>>>>These are just my initial thoughts...comments and CC> > feedback welcome! CC> > > >>>>>> CC> > > >>>>>>Christian CC> > > >>>>>>---------------------------------------------- CC> > > >>>>>>Christian Cryder [[email protected]] CC> > > >>>>>>Internet Architect, ATMReports.com CC> > > >>>>>>Barracuda - http://barracuda.enhydra.org CC> > > >>>>>>---------------------------------------------- CC> > > >>>>>>"Coffee? I could quit anytime, just not today" CC> > > >>>>>> CC> > > >>>>>>_______________________________________________ CC> > > >>>>>>Barracuda mailing list CC> > > >>>>>>[email protected] CC> > > >>>>>>http://barracudamvc.org/lists/listinfo/barracuda CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>> CC> > > >>>>>_______________________________________________ CC> > > >>>>>Barracuda mailing list CC> > > >>>>>[email protected] CC> > > >>>>>http://barracudamvc.org/lists/listinfo/barracuda CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>> CC> > > >>>>_______________________________________________ CC> > > >>>>Barracuda mailing list CC> > > >>>>[email protected] CC> > > >>>>http://barracudamvc.org/lists/listinfo/barracuda CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>> CC> > > >>>_______________________________________________ CC> > > >>>Barracuda mailing list CC> > > >>>[email protected] CC> > > >>>http://barracudamvc.org/lists/listinfo/barracuda CC> > > >>> CC> > > >>> CC> > > >>_______________________________________________ CC> > > >>Barracuda mailing list CC> > > >>[email protected] CC> > > >>http://barracudamvc.org/lists/listinfo/barracuda CC> > > >> CC> > > >> CC> > > > CC> > > >_______________________________________________ CC> > > >Barracuda mailing list CC> > > >[email protected] CC> > > >http://barracudamvc.org/lists/listinfo/barracuda CC> > > > CC> > > > CC> > > > CC> > > > CC> > > CC> > > _______________________________________________ CC> > > Barracuda mailing list CC> > > [email protected] CC> > > http://barracudamvc.org/lists/listinfo/barracuda CC> > CC> > _______________________________________________ CC> > Barracuda mailing list CC> > [email protected] CC> > http://barracudamvc.org/lists/listinfo/barracuda CC> _______________________________________________ CC> Barracuda mailing list CC> [email protected] CC> http://barracudamvc.org/lists/listinfo/barracuda -- Best regards, Jacob mailto:[email protected]