latest mods. Release material? You decide...
Jacob Kjome <[email protected]>
| Newsgroups | gmane.comp.java.enhydra.barracuda.general |
|---|---|
| Message-ID | <[email protected]> |
Hi everyone, I've modified some stuff about XMLC and simplified deployment. First, I've now added an xmlc-all-runtime.jar which includes the contents of the xmlc-specific xmlc, xerces, xhtml, and wireless jars. As such, I've removed the latter jars. This makes dealing with XMLC a bit easier. You can still access separate jars from the XMLC project (use current CVS if you do as I've made changes post-beta1), but this just makes things easier. There is no xerces jar file that needs to be added to shared/lib or anything like that. Barracuda is now completely self sufficient as a WAR (other than Xerces2 and parser api's which is not really a problem....see below). Second, I completely removed all vestiges of the endorsed packages from the XMLC's xerces (as well as the com.lutris package). This means that there is no issue with putting this jar in WEB-INF/lib....which is what allowed for the singe xmlc-all-runtime.jar file in the first place. This does mean that you will need xmlParserAPIs.jar or xml-apis.jar in the build and runtime classpaths (unless you use j2sdk1.4.x which already has these libraries, but I haven't done much testing of that yet). You'll also need xercesImpl.jar (Xerces2) for certain parts of Barracuda which specify an apache parser to use. For instance, the web.xml references an apache parser for parsing the event gateway application descriptor. This shouldn't be a problem since Ant and Tomcat come with Xerces by default. Anway, if people could try things out, that would be great. Report any problems (I don't forsee any). If everything is well, we can tag CVS and one of the admins can add the 1.2.0 release files to the downloads directory. Jake