tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 52324] New: IncompatibleClassChangeError
Date Tue, 13 Dec 2011 17:02:55 GMT

             Bug #: 52324
           Product: Tomcat 7
           Version: unspecified
          Platform: PC
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
    Classification: Unclassified

Due to artifact '' changing type
(from abstract class to interface) between the Tomcat 6 and 7 API:s you can no
longer deploy web applications containing certain libraries (such as a bit
older JBoss client libraries) when there are also web fragments (or web.xml
files with a version >= 2.5) present.

This is due to web fragments / modern web.xml files triggering a scan of the
entire classpath looking for annotations. The following exception is the result
(the message is quite clear):

java.lang.IncompatibleClassChangeError: class
org.jboss.remoting.transport.coyote.ssl.RemotingServerSocketFactory has
interface as super class

Replacing the web fragment with a web.xml of version <= 2.4 does not trigger
the error (since Tomcat and other containers deem such web applications as
'legacy-style', and therefore does not scan the classpath for annotations).

Was this change (quite API-breaking) of type for ServerSocketFactory
deliberate? I can't seem to find anything in the general changenotes regarding
this change, though it might have been noted somewhere else, or in an earlier
version even.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message