You most likely have not configured the Seam resource servlet in web.xml but you should anyway use Seam 2.2.x and look at /examples/restbay.

Hi Rakesh,

Your included code misses the @Name annotation on the class definition. Maybe that is your problem?

Seam 2.1.2 works great with RestEasy, don't try it with earlier releases (I mean pre 2.1.2) because the rest-services tend to fail spontaneously after multiple deploys. Basiscally  there is no need to use 2.2.0 (yet..)

I've included one of my beans to compare:

public interface ExportRest {

     @GET
     @Path("/")
     @Produces("text/xml")
     public TrafficIncidentOverview export();
}

The TrafficIncidentOverview is a JAXB-annotated class which provides the XML-root for a collection of Incidents:

@XmlAccessorType(XmlAccessType.FIELD)
@XmlRootElement(name = "TrafficIncidentOverview")
public class TrafficIncidentOverview {

    @XmlElement(required = true) 
     protected List<TrafficIncident> incident = new ArrayList<TrafficIncident>();

    @XmlTransient
     public List<TrafficIncident> getOverview() {
          return incident;
     }

     public void setOverview(List<TrafficIncident> overview) {
          this.incident = overview;
     }
     
}

The request is the simple http://mydomain/MyApplication/seam/resource/rest/export and it streams out a collection of incidents with attributes in XML-format. That's it.

@Name("exportHandler")
@AutoCreate
@Path("/export")
public class ExportRestHandler implements ExportRest {

     @Logger Log log;
     @In EntityManager entityManager;

     @Create
     public void create() {
          log.info("export-Handler created");
     }
     @Destroy
     public void destroy() {
          log.info("export-Handler destroyed");
     }

     @Transactional
     @Override
     public TrafficIncidentOverview export() {

          List<TrafficIncident> list = entityManager.createQuery(
                    "select distinct i from TrafficIncident i "
                              + " left join fetch i.location.geoPoint l "
                              + " where i.closureTimestamp is null").getResultList();

          TrafficIncidentOverview view = new TrafficIncidentOverview();
          view.setOverview(list);
          return view;
     }

}

Hopefully you get it working, because it an amazing tool which saves you a lot of time.

Success !

Leo

Hi Rakesh,

The jars are ok so it should work, what surprises me is that you have a response with an url stating that it can't find the resouce with restv1 in the string. This looks as there is a setting in your components.xml whic causes that.

So you can:
(1) check if the resource is available under http://localhost:8080/Restful/seam/resource/restv1/customer/1 : notice the change to restv1 and
(2) see if the following exists in components.xml:

<resteasy:application resource-path-prefix="/restv1" />

Nothing to worry, because adding a version number is great for maintenance!

Hi Rakesh,

Nice puzzle you have...

The only thing I see different is the @Produces annotation where you say that it will be text/xml, but you are actually sending text/plain.

Try if it reaches the method with some additional debugging. So create a second method with no parameters and a signature of /test (or whatever other name.

Add the following simple code to the bean:

import org.jboss.seam.annotations.Logger;
import org.jboss.seam.log.Log;

@Logger Log log;

@Create
public void create(){
log.info("Bean created");
}
@Destroy
public void destroy(){
log.info("Bean destroyed");
}

Now you're able to see if something is happening. When you hit the browser, the bean should be created and it gives you the create message. After that if will give you the reply from the test-method and after that the destroy method.

So basically if you get create-message, an error and the destroy message, the bean is ok, but there is something wrong with you mapping.

Leo

And additionally, see if the deployed application name is the same as the one you're using in the URL. Just go to the root http://localhost:8080 and you should see and answer from your server. If you have an index-file (or whatever startup html file)  in the root of your application. http://localhost:8080/Restful should give an answer.

Leo 

Is there a reason why you do not tell us about or even look at the messages in the log? It's all there: registration of resources on startup, resolving resources during a request, and so on.

Rakesh Yadav wrote on Nov 04, 2009 16:22:

public interface MyCustomerResource 
{
    @GET
    @Path("/{customerId}")
    @Produces("text/xml")
    public String getCustomer(@PathParam("customerId") int id);
}

@Path("/customer")
@Name("customerResource")
public class MyCustomerResourceBean implements MyCustomerResource {
   
    public String getCustomer(int id) {
         return "hello";
    }
}

This is wrong. @Path always goes on the interface, not the implementation class. Read the documentation! Use the log messages!

Enable DEBUG or even TRACE logging for the org.jboss.seam.resteasy category. Use Google first before asking how to do that.