Errors when upgrading to JBoss 5 AS
There seem to be a few changes, even from 5.0.0.CR1 and CR2 to 5.0.1.GA.
First off, I was able to have copies of xerces in my WEB-INF/lib folders before I upgraded (didn't need them there, JBoss has it's own), and they throw an error now. I assume some sorta classloading change took place, probably for the better, so right on. Removing 'em solves that.
Secondly, I had to be sure my EAR META-INF/application.xml files were using the 5 standard, while they were are 1.2 before. Here's an example of an application.xml for 5:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
version="5">
<description>jasperserver 3.0</description>
<module id="WebModule_1">
<web>
<web-uri>jasperserver.war</web-uri>
<context-root>/jasperserver</context-root>
</web>
</module>
</application>
<application xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"
version="5">
<description>jasperserver 3.0</description>
<module id="WebModule_1">
<web>
<web-uri>jasperserver.war</web-uri>
<context-root>/jasperserver</context-root>
</web>
</module>
</application>
Updating to that standard was pretty easy, you can be sure it validates by using an XML editor that rocks, but I just used logic (what's the same, what's different).
That's about all I've come across so far.
There are no comments for this entry.
[Add Comment] [Subscribe to Comments]