Open Source Document Management System | OpenKM

Hi,
We were not able to deploy OpenKM 6.3 in any version of the JBoss, tried with different version of JBoss

Only OpenKM-5.1.10_JBoss-4.2.3.GA bundle Community Edition is available in the market, but this is also throwing exception while retrieving documents from the repository.

Following are the exceptions that got raised when tried deploying with different versions of JBoss server.

1. JBoss AS 7 / JBoss AS 6 - Error :

Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.jaxws.JaxWsConfigurationException: The @javax.jws.WebMethod(
exclude=true) cannot be used on a service endpoint interface. Method: createType

2. JBoss 5 Error :

10:44:11,644 ERROR [StandardContext] Context [/OpenKM] startup failed due to previous errors
java.lang.RuntimeException: mapped-name is required for org.apache.cxf.jaxws.context.WebServiceContextResourceResolver/b
us of deployment OpenKM.war

3. JBoss Portal Server 2.7.2 Error :

Able to launch and login. But getting exception while documents retrieved.
This is same error what we have in OpenKM-5.1.10_JBoss-4.2.3.GA bundle.

4. JBoss-4.2.3.GA (OpenKM 6.3)

Able to launch and login. But getting exception while documents retrieved.
This is same error what we have in OpenKM-5.1.10_JBoss-4.2.3.GA bundle.

Please suggest me how to do it.

Thanks,
Vittal

From version 6.0.X we discontinued the OpenKM bundle with JBoss due the lot of problems we got with JBoss webservices and other issues what caused a lot of problems between JBoss migration. Other reason was performance and really OpenKM does not need almost features with what comes by default JBoss. For it reason we've discontinued the bundle and we suggest use Tomcat bundle.

If you want to get OpenKM running in JBoss should be changed some XML descriptors to deploy application under JBoss and also probably is needed doing some minimal changes in source code. If you want to get running in JBoss you should configure development environment and work on it to get it running. If you provide us some patches we will study and if are right we will apply or share with other community users interested in this feature. But I want to be clear with you. We will not maintaining this integration.