|
|
XMLC and Xerces 2: msg#00036
java.enhydra.xmlc
|
Subject: |
XMLC and Xerces 2 |
> I guess
that we can use this as an incentive to migrating XMLC to Xerces2 instead of
Xerces1.
I'd
like to open a discussion on this...can we establish a time frame for getting
XMLC to Xerces 2? This would be tremendously helpful in terms of integrating
with modern appservers (and JDK 1.4)
Christian
----------------------------------------------
Christian Cryder
[christianc@xxxxxxxxxxxxxx]
Internet Architect, ATMReports.com
Barracuda -
http://barracudamvc.org
----------------------------------------------
"Coffee?
I could quit anytime, just not today"
Just a note. The issue is
having xercesImpl.jar and xmlParserAPIs.jar in CATALINA_HOME/common/endorsed
while the xerces version XMLC uses is in CATALINA_HOME/shared/lib. The
remedy is to stop Tomcat, remove the jars from common/endorsed, and restart
Tomcat. Everything will work fine then.
I have made some
notes as to why this is on the BarracudaMVC list:
http://barracudamvc.org/lists/archives/barracuda/2003-January/005749.html
If
David Li and Richard Kunze (and others, of course) could take a look at the
issue, that would be fantastic. If it could be solved in a way which
allows us to leave the jars in common/endorsed, it would make it that much
easier to provide instructions for deploying XMLC/Barracuda apps on
Tomcat. If it can't be fixed in the code, at least we have a
workaround...but it isn't ideal. I guess that we can use this as an
incentive to migrating XMLC to Xerces2 instead of
Xerces1.
Jake
At 04:51 PM 1/16/2003 -0700, you wrote:
Hey folks,
Anyone want to
comment on the following error we've just noticed in
Barracuda?
Basically, everything seems to be working fine with regular HTML
files
that are compiled via XMLC. As soon as we even reference an XML
file
compiled by XMLC, however, the following error occurs:
>
----- Root Cause -----
> java.lang.IllegalAccessError: tried to access
method
>
org.apache.xerces.dom.DocumentTypeImpl.setOwnerDocument(Lorg/apach
>
e/xerces/dom/CoreDocumentImpl;)V from class org.enhydra.xml.
>
lazydom.LazyDocumentType
> at
org.enhydra.xml.lazydom.LazyDocumentType.setOwnerDocument(
>
LazyDocumentType.java:74)
> at
org.enhydra.xml.lazydom.LazyDocument.<init>(LazyDocument.
>
java:123)
> at
org.enhydra.xml.xmlc.dom.lazydom.LazyDomFactory.createDocu
>
ment(LazyDomFactory.java:94)
> at
org.enhydra.barracuda.tutorials.xmlc.HelloWorld3XML.buildT
>
emplateSubDocument (Unknown Source)
> at
org.enhydra.barracuda.tutorials.xmlc.HelloWorld3XML.<clini
>
t>(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.handleDef
>
ault(HelloWorld3.java:64)
> at
org.enhydra.barracuda.core.comp.helper.ComponentGateway.ha
>
ndleDefault(ComponentGateway.java:261)
> at
org.enhydra.barracuda.core.comp.helper.ComponentGateway.do
>
Get(ComponentGateway.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...
I know this used to work just fine (pre XMLC
2.1?)
Christian
----------------------------------------------
Christian
Cryder [christianc@xxxxxxxxxxxxxx]
Internet Architect,
ATMReports.com
Barracuda - http://barracuda.enhydra.org
----------------------------------------------
"Coffee?
I could quit anytime, just not today"
> -----Original
Message-----
> From: barracuda-admin@xxxxxxxxxxxxxxxx
> [mailto:barracuda-admin@xxxxxxxxxxxxxxxx]On Behalf Of
Christian Cryder
> Sent: Thursday, January 16, 2003 4:39 PM
>
To: barracuda@xxxxxxxxxxxxxxxx
> Subject: RE: [Barracuda] Examples not
working
>
>
> Hmmm...here's some more
detail:
>
>
> Christian
>
----------------------------------------------
> Christian Cryder
[christianc@xxxxxxxxxxxxxx]
> Internet Architect,
ATMReports.com
> Barracuda - http://barracuda.enhydra.org
>
----------------------------------------------
> "Coffee? I could quit
anytime, just not today"
>
> > -----Original
Message-----
> > From: barracuda-admin@xxxxxxxxxxxxxxxx
>
> [mailto:barracuda-admin@xxxxxxxxxxxxxxxx]On Behalf Of
Christian Cryder
> > Sent: Thursday, January 16, 2003 4:21
PM
> > To: barracuda@xxxxxxxxxxxxxxxx
> > 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
[christianc@xxxxxxxxxxxxxx]
> > Internet Architect,
ATMReports.com
> > Barracuda - http://barracuda.enhydra.org
> >
----------------------------------------------
> > "Coffee? I could
quit anytime, just not today"
> >
> > > -----Original
Message-----
> > > From:
barracuda-admin@xxxxxxxxxxxxxxxx
> > > [mailto:barracuda-admin@xxxxxxxxxxxxxxxx]On Behalf Of
Denny Chambers
> > > Sent: Thursday, January 16, 2003 3:52
PM
> > > To: barracuda@xxxxxxxxxxxxxxxx
> > >
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 [christianc@xxxxxxxxxxxxxx]
> > >
>Internet Architect, ATMReports.com
> > > >Barracuda - http://barracuda.enhydra.org
> > >
>----------------------------------------------
> > >
>"Coffee? I could quit anytime, just not today"
> > >
>
> > > >
> > > >
> > >
>>-----Original Message-----
> > > >>From:
barracuda-admin@xxxxxxxxxxxxxxxx
> > > >>[mailto:barracuda-admin@xxxxxxxxxxxxxxxx]On Behalf
Of
> Christian Cryder
> > > >>Sent: Thursday,
January 16, 2003 3:02 PM
> > > >>To:
barracuda@xxxxxxxxxxxxxxxx
> > > >>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 [christianc@xxxxxxxxxxxxxx]
> > >
>>Internet Architect, ATMReports.com
> > >
>>Barracuda - http://barracuda.enhydra.org
> > >
>>----------------------------------------------
> > >
>>"Coffee? I could quit anytime, just not today"
> > >
>>
> > > >>
> > > >>
> >
> >>>-----Original Message-----
> > >
>>>From: barracuda-admin@xxxxxxxxxxxxxxxx
> > >
>>>[mailto:barracuda-admin@xxxxxxxxxxxxxxxx]On Behalf
Of
> Denny Chambers
> > > >>>Sent: Thursday,
January 16, 2003 2:55 PM
> > > >>>To:
barracuda@xxxxxxxxxxxxxxxx
> > > >>>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
[christianc@xxxxxxxxxxxxxx]
> > > >>>>Internet
Architect, ATMReports.com
> > > >>>>Barracuda - http://barracuda.enhydra.org
> > >
>>>>----------------------------------------------
> >
> >>>>"Coffee? I could quit anytime, just not today"
>
> > >>>>
> > > >>>>
> >
> >>>>
> > > >>>>
> > >
>>>>
> > > >>>>>-----Original
Message-----
> > > >>>>>From:
barracuda-admin@xxxxxxxxxxxxxxxx
> > > >>>>>[mailto:barracuda-admin@xxxxxxxxxxxxxxxx]On Behalf
Of
> > Denny Chambers
> > > >>>>>Sent:
Thursday, January 16, 2003 1:17 PM
> > > >>>>>To:
barracuda@xxxxxxxxxxxxxxxx
> > > >>>>>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
[christianc@xxxxxxxxxxxxxx]
> > >
>>>>>>Internet Architect, ATMReports.com
> > >
>>>>>>Barracuda - http://barracuda.enhydra.org
> > >
>>>>>>----------------------------------------------
>
> > >>>>>>"Coffee? I could quit anytime, just not
today"
> > > >>>>>>
> > >
>>>>>>_______________________________________________
>
> > >>>>>>Barracuda mailing list
> > >
>>>>>>Barracuda@xxxxxxxxxxxxxxxx
> > >
>>>>>>http://barracudamvc.org/lists/listinfo/barracuda
>
> > >>>>>>
> > >
>>>>>>
> > > >>>>>>
>
> > >>>>>>
> > >
>>>>>>
> > > >>>>>>
>
> > >>>>>>
> > >
>>>>>>
> > >
>>>>>_______________________________________________
>
> > >>>>>Barracuda mailing list
> > >
>>>>>Barracuda@xxxxxxxxxxxxxxxx
> > >
>>>>>http://barracudamvc.org/lists/listinfo/barracuda
>
> > >>>>>
> > >
>>>>>
> > > >>>>>
> >
> >>>>>
> > >
>>>>_______________________________________________
> >
> >>>>Barracuda mailing list
> > >
>>>>Barracuda@xxxxxxxxxxxxxxxx
> > >
>>>>http://barracudamvc.org/lists/listinfo/barracuda
>
> > >>>>
> > > >>>>
> >
> >>>>
> > > >>>>
> > >
>>>>
> > > >>>>
> > >
>>>_______________________________________________
> >
> >>>Barracuda mailing list
> > >
>>>Barracuda@xxxxxxxxxxxxxxxx
> > > >>>http://barracudamvc.org/lists/listinfo/barracuda
>
> > >>>
> > > >>>
> > >
>>_______________________________________________
> > >
>>Barracuda mailing list
> > >
>>Barracuda@xxxxxxxxxxxxxxxx
> > > >>http://barracudamvc.org/lists/listinfo/barracuda
>
> > >>
> > > >>
> > > >
>
> > >_______________________________________________
> >
> >Barracuda mailing list
> > >
>Barracuda@xxxxxxxxxxxxxxxx
> > > >http://barracudamvc.org/lists/listinfo/barracuda
>
> > >
> > > >
> > > >
> >
> >
> > >
> > >
_______________________________________________
> > > Barracuda
mailing list
> > > Barracuda@xxxxxxxxxxxxxxxx
> > >
http://barracudamvc.org/lists/listinfo/barracuda
>
>
> > _______________________________________________
>
> Barracuda mailing list
> > Barracuda@xxxxxxxxxxxxxxxx
>
> http://barracudamvc.org/lists/listinfo/barracuda
>
>
_______________________________________________
> Barracuda mailing
list
> Barracuda@xxxxxxxxxxxxxxxx
> http://barracudamvc.org/lists/listinfo/barracuda
_______________________________________________
XMLC
mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| |
