Re: xerces-1.4.4-xmlc-2.2.jar so hard to find

Jacob Kjome <[email protected]>
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
Hi Andras,

I think you mean the 1.2.0 release of Barracuda.

Actually, the xerces jar has been wrapped into the 
xmlc-all-runtime-2.2.jar.  In the XMLC (latest CVS or the tag 
"XMLC_2_2_POST_BETA_1_BARRACUDA_1_2_0") build, you can run the 
"lib-all-runtime" target to build this jar.  You actually should be using 
jars created from the above mentioned tagged release of XMLC instead of the 
XMLC-2.2beta1 release of XMLC.  I made some important fixes after the beta1 
was released.  Of course, you can just use the jars that come with 
Barracuda.  See more information below...


Please read the following for more information from A_Changes_History.java....
<quote>
jrk_20030520.1 - Further updated XMLC to fix a couple bugs. Completely 
removed endorsed packages (javax.*, org.xml.*, org.w3c.dom.*) from XMLC's 
xerces package. This makes it so XMLC's xerces can exist in WEB-INF/lib. 
Simplified XMLC by moving xmlc jars (xmlc, xerces, xhtml, wireless) into on 
jar called xmlc-all-runtime.jar. There is no more need to copy the xerces 
jar to and external shared classloader. Note that all XMLC jars including 
jtidy, gnu-regexp, xmlc-all-runtime, and xmlc-taskdef are based on the XMLC 
CVS source with the tag XMLC_2_2_POST_BETA_1_BARRACUDA_1_2_0.
</quote>

Also see the following from the changes.html file...
<quote>
Support for XMLC-2.2. This makes it so that Barracuda/XMLC apps finally 
won't conflict with Xerces2 which most app servers and Ant use. This is 
because XMLC's Xerces package has been moved into the org.enhydra.apache 
package, effectively hiding XMLC's Xerces implementation from other Xerces 
implementations. Additionally, XMLC no longer includes any endorsed 
packages. These need to be provided either via j2sdk1.4.x or via a the 
inclusion of, for instance, xmlParserAPIs.jar or xml-apis.jar which comes 
with Xerces2. Also, at runtime, Barracuda currently depends on Xerces2 
because the Xerces SAX parser is specified in the web.xml to read the 
assembly descriptor. Either way, if you create documents outside the scope 
of using XMLC, you will need some DOM implementation. Xerces2 is a fine 
choice. Xerces2 can be in common/endorsed on Tomat and ANT_HOME/lib in Ant 
and everything will work just fine.
</quote>


Hope that clears things up.

Jake

At 03:03 PM 6/9/2003 +0300, you wrote:
>     Hi list,
>
>I am using the curent release (1.0.2) of Barracuda and i had a hard time
>finding this jar:
>xerces-1.4.4-xmlc-2.2.jar
>Why this file wasn't included in the 1.0.2 release?(some license isssues??)
>Actually i downloaded
>http://download.debian-sf.objectweb.org/xmlc/xmlc-2.2.beta.1.tar.gz
>and here i found a xerces.jar, i hope this is the one.
>
>Thank you,
>
>Andras.
>
>
>
>_______________________________________________
>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.