RE: Examples not working

"Christian Cryder" <[email protected]>
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
HelloWorld3 should now be working. Cool! Thanks to Denny and Jake in finding
and fixing this...

Christian
----------------------------------------------
Christian Cryder [[email protected]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"
  -----Original Message-----
  From: [email protected]
[mailto:[email protected]]On Behalf Of Christian Cryder
  Sent: Friday, January 17, 2003 9:44 AM
  To: [email protected]
  Subject: RE: [Barracuda] Examples not working


  Ok, so with xalan and xerces OUT of my Barracuda's WEB-INF/lib, I still
get the error on HelloWorld3. Now, these jars ARE installed in Tomcat's
shared/lib.

  So, I moved these to Tomcat's endorsed directory, and voila! everything
works again!

  Ok, very cool...I will upgrade accordingly on the server and check it out
up there as well. We probably need to come up with a nice, clean install doc
that explains exactly what to put where...I'll try and do that this weekend.

  Thanks for your help on this!

  Christian

  ----------------------------------------------
  Christian Cryder [[email protected]]
  Internet Architect, ATMReports.com
  Barracuda - http://barracudamvc.org
  ----------------------------------------------
  "Coffee? I could quit anytime, just not today"

    -----Original Message-----
    From: [email protected]
[mailto:[email protected]]On Behalf Of Jacob Kjome
    Sent: Thursday, January 16, 2003 10:38 PM
    To: [email protected]
    Subject: RE: [Barracuda] Examples not working



    Hmm.... one thing I stated in my previous email about Xerces and Xalan
was that "Currently, by some luck and some super coding from Richard Kunze,
we are able to put our version of Xerces in shared/lib even while Xerces2 is
in common/endorsed".  Well, as it turns out, this seems true in every case
except the one dealing with the XMLC templates compiled from XML files
rather than HTML files.

    The fix is quite simple.  Remove xercesImpl.jar and xmlParserAPIs.jar
from CATALINA_HOME/common/endorsed.  It will work perfectly, I promise.  Or,
you can always use the JDK1.4-lite version of Tomcat.  However, that
excludes more libs than just the xml parser and I'd suggest using the full
version and deleting the jars as stated previously.

    Now, I know that this was a problem even with XMLC compiled HTML files
at one point before Richard Kunze made some modifcations to allow xerces to
be in shared/lib even when Xerces2 was in common/endorsed.  I just can't
remember what those mods were?

    Richard, if you are reading this, could you expound on what you did to
make the latter case work?  Can the same be done for the case of XMLC
compiled XML templates?  Hopefully you remember the change you made (and the
conversation we had about it).

    The other stuff about not putting xerces and xalan (or any of the xmlc
classes, IMO) in WEB-INF/lib is still completely valid and has little to do
with this issue.  The should be in shared/lib and nowhere else.


    Jake

    At 04:38 PM 1/16/2003 -0700, you wrote:

      Hmmm...here's some more detail:

      ----- Root Cause -----
      java.lang.IllegalAccessError: tried to access method

org.apache.xerces.dom.DocumentTypeImpl.setOwnerDocument(Lorg/apache/xerces/d
      om/CoreDocumentImpl;)V from class
org.enhydra.xml.lazydom.LazyDocumentType
              at

org.enhydra.xml.lazydom.LazyDocumentType.setOwnerDocument(LazyDocumentType.j
      ava:74)
              at
org.enhydra.xml.lazydom.LazyDocument.<init>(LazyDocument.java:123)
              at

org.enhydra.xml.xmlc.dom.lazydom.LazyDomFactory.createDocument(LazyDomFactor
      y.java:94)
              at

org.enhydra.barracuda.tutorials.xmlc.HelloWorld3XML.buildTemplateSubDocument
      (Unknown Source)
              at
org.enhydra.barracuda.tutorials.xmlc.HelloWorld3XML.<clinit>(Unknown
      Source)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:140)
              at

org.enhydra.barracuda.tutorials.comp.HelloWorld3.class$(HelloWorld3.java:64)
              at

org.enhydra.barracuda.tutorials.comp.HelloWorld3.handleDefault(HelloWorld3.j
      ava:64)
              at

org.enhydra.barracuda.core.comp.helper.ComponentGateway.handleDefault(Compon
      entGateway.java:261)
              at

org.enhydra.barracuda.core.comp.helper.ComponentGateway.doGet(ComponentGatew
      ay.java:170)
              at
javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

      Looks to me like there is something in the current version of XMLC
(2.1)
      which is choking on the XML doc types. Its possible that this was
introduced
      in the last version of XMLC and just not caught until now...Jake -
you've
      spent some time looking at the internals of XMLC; any thoughts here?

      I'll look at htis more later once I get a bit of time...

      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 4:21 PM
      > To: [email protected]
      > Subject: RE: [Barracuda] Examples not working
      >
      >
      > Wierd...I'm getting that same error here locally too...I'll have
      > to look at
      > this more closely...maybe tonight. Seems to be dying on this line
right
      > here:
      >
      >         Class pageCl = HelloWorld3XML.class;
      >
      > But that class is clearly sitting there in the classpath. Hmmm....
      >
      > 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 3:52 PM
      > > To: [email protected]
      > > Subject: Re: [Barracuda] Examples not working
      > >
      > >
      > > 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
      > > >
      > > >
      > > >
      > > >
      > >
      > > _______________________________________________
      > > 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.