The path "C:\jboss-5.1.0.GA\server\default\deploy\is-bcl-ear-1.0" does not have the ".ear" extension. Is this on purpose?
Which files/directories are packed and which are exploded?
Check if the file jboss-seam-debug-2.2.0.GA. jar is in your lib directory in your WAR file.
The error message does state that is not. If not just put this file in your lib directory.
I am having the same problem as Joshua and in my case I can assure that the ear exists under the path displayed in the FileNotFoundException, the strange thing is that it seems like Seam is trying to treat it like a regular file instead of a resource available on classloader. Has anyone found a solution for this? I wasn't really wondering to have a different packaging for JBoss (it also does not make much sense).
Seam seems to work on JBoss only if you dont place any of their jar files and use the ones already on JBoss classpath.
The folder is-bcl-ear-1.0 contained the jar and war files in unpacked format.
jboss-seam-debug-2.2.0.GA. jar was available inside the package in a packed format.
I guess the class loader expects the deployed entities to have the appropriate extension. In this case, it should have been is-bcl-ear-1.0.ear.
There were too many issues and hence we migrated to deploying the application in a packed format (i.e. is-bcl-ear.ear) every time.