#90 Modify sip.xml and web.xml to work with MSS

[Tom Smith]

Mobicents SIP Servlets has changed its processing of deployment descriptors since 1.0. Here are the changes required to interoperate with MSS 1.3.1+:

* Change sip.xml so that sip-app tag reads:

<sip-app xmlns="http://www.jcp.org/xml/ns/sipservlet" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jcp.org/xml/ns/sipservlet http://www.jcp.org/xml/ns/sipservlet/sip-app_1_1.xsd" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.1">

* Add <distributable/> tag after <app-name> in sip.xml (Seems like this is a MSS bug)

* Add <distributable/> tag after <app-name> in web.xml (Seems like this is a MSS bug)

* Remove <javaee:display-name> tag from sip.xml (MSS bug, or just misplaced?)

Once we settle on a format that works with all target containers, we will need to change example features as well as appgen.

[Eric]

Is this now no longer an issue with MSS/Tomcat 1.5 and 1.6? i.e. .war files built with the ant fatsar target out of the box now deploy correctly in MSS/Tomcat? If so, we should close this artifact.

(there are separate issue with MSS/JBoss 1.5 and 1.6, but it should be tracked separately.)