> I've been working to get Catalina(Tomcat) and JBoss working together using > the exisiting integration framework in contrib. JBoss starts ok and seems > healthy, but Catalina wont deploy any applications including the example > application that comes with it. It complains of 'sealing violation's when > trying to load classes. > > Has anyone run across this before and have pointers to a fix? See below for > a stack trace from the Catalina log. My current strategy is to look for > redundant jar files in both Catalina and JBoss and move them aside, but this > seems a bit of a hack. We've seen this where I work, although not specifically with jboss or tomcat. In our situation it was the xalan jar and some other jar, loaded by two different class loaders (one in the jre's lib/ext directory and the other in JavaWebServer's lib directory) where one of these jars depended on the classes provided by the other. I forget the details. It came down to one line in the manifest file of a single jar. The line just said "sealed". We unjared, removed that line, and re-created the jar. The problem was solved. http://java.sun.com/docs/books/tutorial/jar/ > > * Package Sealing (version 1.2): Packages stored in JAR files can be > optionally sealed so that the package can enforce version > consistency. Sealing a package within a JAR file means that all > classes defined in that package must be found in the same JAR file. I think the culprit in our case was the xalan jar. ---- [EMAIL PROTECTED] _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
