Hi, obvious things missing from WildFly are ones that ware removed: - cmp, removed, as it is no longer EE7 requirement - jaxr, removed, as it is no longer EE7 requirement - osgi, removed as it was moved to separate project and can be re-added manually However the big thing we changed in WildFly is replacement of web server from jbossweb to undertow (web subsystem to undertow subsystem). There ware many things that ware integrated with jbossweb in it's specific way (using valves for example) and things like that need to be migrated / updated to be compatible with undertow. Issue you linked is case of such incompatibility. It is hard to determine how many other projects were relying on jbossweb/tomcat specific APIs so producing any list would be quite hard. All we could do is crate wiki page that list external projects and its compatibility status. My opinion is that beyond some custom auth mechanisms (what picketlink does for example) most of things should work. As auth mechanisms APIs ware one thing that (w)are tied to servlet container. -- tomaz On Thu, Jan 9, 2014 at 11:20 AM, Jaromir Hamala <jaromir.hamala(a)gmail.com&gt;wrote:

Hi, thanks a lot for the replies! I suppose having such list would be beneficial for a lot of people. "Migration Considerations" or something like this. I can see there are two kinds of potential issues: 1. missing or changed (CMP, JAXR, JBossWeb Valves, etc) API 2. missing "features" - or generally stuff on somewhat higher level than Java API - such as the SAML issue - it may or may not be the result of the API changes. This can be somewhat tricky to identify, but I believe it should be documented if the feature was part of the JBoss AS 7 distribution. Cheers, Jaromir On Thu, Jan 9, 2014 at 10:56 AM, arjan tijms <arjan.tijms(a)gmail.com&gt; wrote: -- “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” Antoine de Saint Exupéry