Struglling to see why it isn't being deployed. Perhaps you could attach the source to your jboss-seam.jar and place a breakpoint in org.jboss.seam.Deployment.Scanner in the Set<Class<?>> getClasses class. Step through this and check that all your classes are loaded by the class loader and then that no error occurs during this process.

Don't worry... I'm pretty sure it's a silly error myself. I'll see what I can do about the debug process outlined above. If there was an error loading a class or somesuch, wouldn't it get reported in the console? Is there a way to set the logger output to a more eplicit level? Would that even help?

The interesting part would be between those two parts, as this is the part that seam scanes the files to see any @Name annotations and then places them in an internal list for reference later on by the JSF pages. It is hear where your deployement is going wrong.

I think you should still pursue the debug.

Also what might be helpful, is if you could make available over the internet the exact ear file that you are using so that myself and others could test it in their environment.