JBossDeveloper

Stuart Douglas wrote:

 

Thats not a JAX-RS webservice, the resteasy configuration should not affect it.

 

JAX-WS is only partly implemented in 7.0, it may be that you have to wait for 7.1

It is true that it is not a JAX-RS service, it is a RESTful service.

Are you suggesting that I stick to JBoss AS 6.0.0.Final until AS 7.1 (it  worked with 6.0)? Is there an expected date for 7.1 release?

When I started the migration, I had the service configured as a Servlet in the web.xml, no RESTEasy nothing. Is that what you are suggesting or are you asking to get rid of the web.xml altogether?

The service seems to be working with a warning during deployment (shown below in deployment log snippet) with the following web.xml. The fact that it did not work with the same web.xml when I started was probably because I was not running the server in standalone preview mode.

It did not work without a web.xml and returned 404.

The warning does not seem to be an issue. However, if you want to investigate, I will gladly provide any information required.

web.xml:

{code:xml}
<web-app 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"
    version="3.0">
    <display-name>movie-service-restful</display-name>
    <servlet>
        <servlet-name>MovieServiceRestful</servlet-name>
        <servlet-class>name.app.abhi.movieservice.restful.service.impl.MovieServiceRestful</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>MovieServiceRestful</servlet-name>
        <url-pattern>/*</url-pattern>
    </servlet-mapping>
</web-app>
{code}

Server log while deployment:

{code}
19:55:51,698 WARN  [org.jboss.wsf.stack.cxf.resolver.JBossWSResourceResolver] (MSC service thread 1-4) Cannot resolve resource: org.apache.cxf.ws.rm.RMManager/bus
19:55:51,707 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) remove: jboss.ws:context=movieservicerestful,endpoint=MovieServiceRestful
19:55:51,726 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment movie-service-restful-1.0-SNAPSHOT.war in 121ms
19:55:51,727 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "movie-service-restful-1.0-SNAPSHOT.war"
19:55:52,439 INFO  [org.jboss.wsf.stack.cxf.deployment.aspect.DescriptorDeploymentAspect] (MSC service thread 1-2) Spring not available, skipping check for user provided jbossws-cxf.xml / cxf.xml configuration files.
19:55:52,441 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-2) Add Service
 id=MovieServiceRestful
 address=http://localhost:8080/movieservicerestful
 implementor=name.app.abhi.movieservice.restful.service.impl.MovieServiceRestful
 invoker=org.jboss.wsf.stack.cxf.InvokerJSE
 serviceName={http://impl.service.restful.movieservice.abhi.app.name/}MovieServiceRestfulService
 portName={http://impl.service.restful.movieservice.abhi.app.name/}MovieServiceRestfulPort
 wsdlLocation=null
 mtomEnabled=false
{code}

Server log after a client request:

I believe this is because java.beans.XMLEncoder works only with Java Beans and TreeSet is not a Java Bean. This is nothing to do with JBoss AS.

{code}
19:56:37,273 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9090-1) java.lang.Exception: Encoder: discarding statement TreeSet.add(Movie);
19:56:37,274 ERROR [stderr] (http-localhost.localdomain-127.0.0.1-9090-1) Continuing ...
{code}