Petar Tahchiev created CMIS-796:
-----------------------------------

             Summary: Runtime descriptor "/WEB-INF/sun-jaxws.xml" is mising
                 Key: CMIS-796
                 URL: https://issues.apache.org/jira/browse/CMIS-796
             Project: Chemistry
          Issue Type: Improvement
          Components: opencmis-server
    Affects Versions: OpenCMIS 0.11.0
            Reporter: Petar Tahchiev


Hi guys,

i'm following this tutorial:

https://github.com/cmisdocs/ServerDevelopmentGuide

on page 22 I saw this:
{code}
mvn archetype:generate \ -DgroupId=org.example.cmis \ -DartifactId=server \ 
-Dversion=1.0-SNAPSHOT \ -Dpackage=org.example.cmis.server \ 
-DprojectPrefix=FileBridge \ -DarchetypeGroupId=org.apache.chemistry.opencmis \ 
-DarchetypeArtifactId=chemistry-opencmis-server-archetype \ 
-DarchetypeVersion=1.0.0-SNAPSHOT \ -DinteractiveMode=false
{code}

so i used it to create my own project. Unfortunately it creates a web.xml with 
this listener:
{code}
    <listener>
        
<listener-class>com.sun.xml.ws.transport.http.servlet.WSServletContextListener</listener-class>
    </listener>
{code}

which seems to require a {{sun-jaxws.xml}} file, which the artifact did not 
create. I managed to find this file in the Chemistry repository, but now I have 
another problem. I'm trying to use Spring's {{WebApplicationInitializer}} and 
get rid of my web.xmls and {{WEB-INF}} folder, and instead package my Cmis 
server as a jar and deploy it in an existing application under {{/cmis}}. 
Unfortunately this is not possible, because I get this exception:
{code}
Caused by: javax.xml.ws.WebServiceException: Runtime descriptor 
"/WEB-INF/sun-jaxws.xml" is mising
        at 
com.sun.xml.ws.transport.http.servlet.WSServletContextListener.contextInitialized(WSServletContextListener.java:107)
{code}

For now I will override the {{WSServletContextListener}} to look for this file 
elsewhere, but please can you improve the code so that it doesn't rely on 
{{WEB-INF}} and on the {{sun-jaxws.xml}} file being there.

Thanks



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to