Databases
StackOverflow2013
Postsdbo
POIntegrating Jetty with RESTEasy
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIntegrating Jetty with RESTEasy
    primarykey
    data
    text
    <p>Any links on how to integrate Jetty and RESTEasy? I am kinda stuck trying to configure RESTEasy with Jetty together....and there seems to be no credible help on the web.</p> <pre><code>public static void main(String[] args) throws Exception { Server server = new Server(8080); WebAppContext context = new WebAppContext(); context.setDescriptor("../WEB-INF/web.xml"); context.setResourceBase("../src/webapp"); context.setContextPath("/"); context.setParentLoaderPriority(true); server.setHandler(context); server.start(); server.join(); } </code></pre> <p>My Web.xml is copied directly from: <a href="http://docs.jboss.org/resteasy/docs/1.0.0.GA/userguide/html/Installation_Configuration.html" rel="noreferrer">http://docs.jboss.org/resteasy/docs/1.0.0.GA/userguide/html/Installation_Configuration.html</a></p> <p>The error I get back is a HTTP 404 when I try to open up a link in my resource file. Everything looks reasonable on the surface, any suggestions?</p> <p>My resource file looks like:</p> <pre><code>package webapp; import javax.ws.rs.GET; import javax.ws.rs.Path; import javax.ws.rs.PathParam; @Path("/*") public class Resource { @GET public String hello() { return "hello"; } @GET @Path("/books") public String getBooks() { return "books"; } @GET @Path("/book/{isbn}") public String getBook(@PathParam("isbn") String id) { return "11123"; } } </code></pre> <p>This is the prints that I see when Jetty starts up:</p> <p>2012-04-10 09:54:27.163:INFO:oejs.Server:jetty-8.1.1.v20120215 2012-04-10 09:54:27.288:INFO:oejw.StandardDescriptorProcessor:NO JSP Support for /, did not find org.apache.jasper.servlet.JspServlet 2012-04-10 09:54:27.319:INFO:oejsh.ContextHandler:started o.e.j.w.WebAppContext{/,file:/C:/Users/xyz/Anotherproj1/src/webapp} 2012-04-10 09:54:27.319:INFO:oejsh.ContextHandler:started o.e.j.w.WebAppContext{/,file:/C:/Users/xyz/Anotherproj1/src/webapp} 2012-04-10 09:54:27.381:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:8080</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USrmoh21
    1. USrmoh21
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIntegrating Jetty with RESTEasy
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POIntegrating Jetty with RESTEasy
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIntegrating Jetty with RESTEasy
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAt first glace this looks correct. Which Jetty Version are you using. Are there any error messages? What's exactly your problem?
      singulars
      1. POIntegrating Jetty with RESTEasy
      1. USandih
    2. CO@andih The error essentially is a HTTP 404 when I try to open up a link in my resource file.
      singulars
      1. POIntegrating Jetty with RESTEasy
      1. USrmoh21
    3. CO@andih I am using Jetty 8.1.1
      singulars
      1. POIntegrating Jetty with RESTEasy
      1. USrmoh21
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload