It's just a basic web.xml generated by the archetype. That's why I'm wondering what servlet mappings I'll need for the ws and the jsf.
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0"
xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<!-- An optional parameter that makes troubleshooting errors much easier -->
<!-- You should remove this context parameter before deploying to production! -->
<context-param>
<param-name>javax.faces.PROJECT_STAGE</param-name>
<param-value>Development</param-value>
</context-param>
<!-- JSF 2.0 Servlet activates automatically when the WEB-INF/faces-config.xml descriptor is present -->
<!-- Enable this mapping to protect your view templates from direct URL access -->
<!--
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>
-->
<session-config>
<session-timeout>60</session-timeout>
</session-config>
<!-- This section is optional. We are allowing index.jsf to handle the root URL (i.e., /). -->
<welcome-file-list>
<!-- Add additional files here, if desired, for example: <welcome-file>index.html</welcome-file> -->
<welcome-file>index.jsf</welcome-file>
</welcome-file-list>
</web-app>