Incompatibilities between current WildFly and EAP 6

Version 1

    Document to record incompatibilities between what's in WildFly and what is in the most recent EAP 6 release.

     

    This is not meant to capture default configuration changes, although if people want to add such things, it's ok, but please create a separate section or something.

     

    Management Changes

     

    JAXR subsystem removal

     

    The JAXR subsystem is no longer supported on servers. Host Controllers can still support the jaxr configuration model, allowing a current version Domain Controller to manage a slave running an EAP 6 release that has servers that use JAXR. But attempting to use the jaxr subsystem on a current version server will fail.

     

    CMP subsystem removal


    The CMR subsystem is no longer supported on servers. Host Controllers can still support the cmp configuration model, allowing a current version Domain Controller to manage a slave running an EAP 6 release that has servers that use CMP. But attempting to use the cmp subsystem on a current version server will fail.


    JBoss Web subsystem removal/replacement by Undertow

     

    The web subsystem is no longer supported on servers. The undertow subsystem now provides HTTP capabilities, including servlet support. Host Controllers can still support the web subsystem configuration model, allowing a current version Domain Controller to manage a slave running an EAP 6 release that has servers that use JBoss Web. But attempting to use the web subsystem on a current version server will fail.


    Note: we are evaluating providing some sort of compatibility layer to allow a legacy web subsystem config to run on a server, a la what's discussed for JACOrb below.

     

    JACOrb subsystem removal/replacement by jdkorb

     

    The jdkorb subsystem is now the default provider of IIOP capabilities, replacing the jacorb subsystem. Host Controllers can still support the full jacorb subsystem configuration model, allowing a current version Domain Controller to manage a slave running an EAP 6 release that has servers that use JACOrb. To help support migration, on servers the jacorb subsystem configuration model will still be supported as much possible, by mapping jacorb configuration notions to jdkorb services. Attempting to use configuration settings that cannot be properly mapped will result in failure.


    TODO link to a doc describing the mapping and what options are no longer supported.

     

    Other Non-Management Changes