RE: Re[2]: Xerces 1 use in XMLC

See comments below...

At 06:11 PM 10/18/2002 -0500, you wrote:
> Hello Jacob,
>  
> > on apache.org?  gnu-regexp is a gnu project, not an apache
> > project.  I think you are talking about Jakarta's reguular
> > expressions package. Totally different, although there isn't 
> > any reason we couldn't use that.  It is just that we use the
> > gnu package instead.
>
> OK, got that. I thought your gnu regexp == jakarta's , but I was
> wrong...
>  
> > What do you mean "considering renaming"?  You can
> rename the  
> > jar files to anything you want.  Call the jtidy package 
> > "mycoolpackage.jar".  It doesn't make a
> difference.  A jar 
> > file is akin to a directory.  You point your classpath to the
> > directory.  The name of that directory doesn't matter, it is
> > what is inside....or am I totally missing your point?
>
> We are thinking of using barracuda as a presentation framework,
> along
> with using axis as our wsdl/web services toolkit. It seems like the
> coexistence of xerces1 (needed by XMLC/barracuda) and xerces2 (needed
> by
> axis) is going to create problems. I am not sure if you can have those
> 2
> versions of parsers in the same VM space (I doubt it...), so I was
> thinking of renaming org.apache.xerces to org.apache.xerces144 in
> the
> xerces-xmlc source files and packaging one xmlc.jar that included 
> it
> all.....
>
> Am I nuts? :)

hmmm..... I'm not sure how that would be done since there are some thing
that were modified in Xerces that were needed as a requirement of
XMLC-2.1 to work.

One thing that might work, in relation with Tomcat-4.1.xx, is to leave
Xerces-2.x.x in $CATALINA_HOME/common/endorsed and put
xerces-1.4.4-xmlc-2.1.jar in $CATALINA_HOME/shared/lib.  That way,
the main parser that will be used is Xerces-2, but the fact that the
1.4.4 parser is also available means that some of the packages that XMLC
uses which only exist in Xerces-1.4.4 and not in Xerces-2 will still be
there for XMLC to utilize while not forcing Xerces-1.4.4 on your other
apps that require Xerces-2.

That said, most apps, if they just use the standard XML parser api's,
should be compatible with either Xerces-1.4.4 or Xerces-2.  XMLC has
a dependency on Xerces-1.4.4 primarily because it uses Xerces extensions
in 1.4.4 which weren't carried over to Xerces-2.  So, you might want
to do a quick test and see if my suggestion above works for your
app.  If it does, then forget about all the renaming stuff as you
would end up having to remap the XMLC source to look at the renamed
Xerces-1.4.4 packages in order to make that approach work.

Let us know how things go.

Jake


> Enrico 
>
> _______________________________________________
> XMLC mailing list
> XMLC@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc