[IllegalArgumentException: VFS000021: path must not be null] when running Seam 2.3 with EAP 6.2.0

Issue

We are trying to migrate our JBoss EAP 5 Seam application to EAP 6.2.0 (upgrade to Seam 2.3.1). During startup, we get the following error:

07:50:05,907 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/appName]] (ServerService Thread Pool -- 62) JBWEB000287: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.IllegalArgumentException: VFS000021: path must not be null
                at org.jboss.vfs.VFS.getChild(VFS.java:175) [jboss-vfs-3.2.2.Final-redhat-1.jar:3.2.2.Final-redhat-1]
                at org.jboss.vfs.VFS.getChild(VFS.java:163) [jboss-vfs-3.2.2.Final-redhat-1.jar:3.2.2.Final-redhat-1]
                at org.jboss.vfs.VFS.getChild(VFS.java:147) [jboss-vfs-3.2.2.Final-redhat-1.jar:3.2.2.Final-redhat-1]
                at org.jboss.seam.integration.jbossas.vfs.VFSScanner.getRoot(VFSScanner.java:64) [jboss-seam-int.jar:6.0.0.GA-redhat-2]
                at org.jboss.seam.integration.jbossas.vfs.VFSScanner.scanResources(VFSScanner.java:151) [jboss-seam-int.jar:6.0.0.GA-redhat-2]
                at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.Final]
                at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.Final]
                at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.Final]
                at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
                at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
                at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
                at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
                at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
                at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [rt.jar:1.6.0_32]
                at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.6.0_32]
                at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.6.0_32]
                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) [rt.jar:1.6.0_32]
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.6.0_32]
                at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_32]
                at org.jboss.threads.JBossThread.run(JBossThread.java:122)

• While migrating epp 4.3.0 application , the following issue was encountered in EAP 6:-

 java.lang.IllegalArgumentException: VFS000021: path must not be null
...
at org.jboss.vfs.VFS.getChild(VFS.java:175) [jboss-vfs-3.2.2.Final-redhat-1.jar:3.2.2.Final-redhat-1]
    at org.jboss.vfs.VFS.getChild(VFS.java:163) [jboss-vfs-3.2.2.Final-redhat-1.jar:3.2.2.Final-redhat-1]