The archive structure of a WAR-based deployment on an servlet engine like Tomcat will look something like this:
my-application.war/
META-INF/
MANIFEST.MF
WEB-INF/
web.xml
components.xml
faces-config.xml
lib/
jboss-seam.jar
jboss-seam-ui.jar
el-api.jar
el-ri.jar
jsf-facelets.jar
myfaces-api.jar
myfaces-impl.jar
jboss-ejb3.jar
jboss-jca.jar
jboss-j2ee.jar
...
mc-conf.jar/
ejb3-interceptors-aop.xml
embedded-jboss-beans.xml
default.persistence.properties
jndi.properties
login-config.xml
security-beans.xml
log4j.xml
my-application.jar/
META-INF/
MANIFEST.MF
persistence.xml
jboss-beans.xml
log4j.xml
seam.properties
org/
jboss/
myapplication/
User.class
Login.class
LoginBean.class
Register.class
RegisterBean.class
...
login.jsp
register.jsp
...
The mc-conf.jar
just contains the standard JBoss Microcontainer configuration files for Embeddable EJB3. You won't usually need to edit these files yourself.
Most of the Seam example applications may be deployed to Tomcat by running ant deploy.tomcat
.