{"id":63,"date":"2012-10-17T14:56:54","date_gmt":"2012-10-17T14:56:54","guid":{"rendered":"http:\/\/blogs.sussex.ac.uk\/coursedata\/?p=63"},"modified":"2012-10-17T15:13:19","modified_gmt":"2012-10-17T15:13:19","slug":"new-features-of-java-ee-6-used-in-this-project-part-2","status":"publish","type":"post","link":"https:\/\/blogs.sussex.ac.uk\/coursedata\/2012\/10\/17\/new-features-of-java-ee-6-used-in-this-project-part-2\/","title":{"rendered":"New features of Java EE 6 used in this project (part 2)"},"content":{"rendered":"

As mentioned in my last post, the XCRI-CAP project has allowed us to use many of the new features of Java EE 6. One of the new features we’ve been able to implement is the RESTful web service support via JAX-RS.\u00a0 Previously we have implemented JAX-WS web services by turning EJB Session beans into web services. For the XCRI-CAP project, we have implemented a RESTful service using the Jersey implementation of JAX-RS<\/a>.<\/p>\n

JAX-RS makes it very easy to produce a RESTful web service. The first thing to do is to register the Jersey REST servlet with the application’s web.xml.<\/p>\n


\n    <servlet>
\n        <servlet-name>JerseyRESTService<\/servlet-name>
\n        <servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer<\/servlet-class>
\n        <init-param>
\n            <param-name>com.sun.jersey.config.property.packages<\/param-name>
\n            <param-value>uk.ac.susx.xcricap.session<\/param-value>
\n        <\/init-param>
\n        <load-on-startup>1<\/load-on-startup>
\n    <\/servlet>
\n    <servlet-mapping>
\n        <servlet-name>JerseyRESTService<\/servlet-name>
\n        <url-pattern>\/CourseCatalog\/*<\/url-pattern>
\n    <\/servlet-mapping><\/code><\/p>\n

This Servlet will be used for any request mapped to \/CourseCatalog.<\/p>\n

Next, we can create an EJB that will act as the actual REST service. Using the @Path annotation at the top of the Session bean will control which requests will be handled by the class. In this instance, I want all requests to \/CourseCatalog to be handled by this Session bean:<\/p>\n

\/**
\n * REST Web Service
\n *
\n * @author rjb41
\n *\/
\n@Path(“\/”)<\/strong>
\n@Stateless
\npublic class XCRI_CAPRestService {<\/p>\n

Next we can write a method that will receive the RESTful requests. The following method handles Rest parameters sent to the \/CourseCatalog\/rest\/foo\/bar URL:<\/p>\n


\n    \/**
\n     * Returns the REST XML representation of the service 
\n     * @todo specify search criteria
\n     * @param cId
\n     * @return 
\n     *\/
\n    @GET
\n    @Path(\"\/rest\/{name}\/{value}\")
\n    @Produces(MediaType.TEXT_XML)
\n    public String getXCRIXml(@PathParam(\"name\") String name, @PathParam(\"value\") String value) {
\n        if (!(new File(xcriSession.getSearchCourseFileName())).exists()) {
\n            xcriSession.createCoursesFile(true);
\n        }
\n        return outputDocument(xcriSession.searchCatalog(name, value)).toString();
\n    }
\n<\/code><\/p>\n

This method treats the first argument as the parameter name and the second as the value to search on, e.g.
\nXCRI-CAP\/CourseCatalog\/rest\/subject\/European would return all courses that contain the word European (the application is actually querying the XML for nodes that end in subject and contain the word ‘European’).<\/p>\n

Of course we can do more complex URL searches but for the purposes of demonstration, this shows what is possible.<\/p>\n

There are plenty of good tutorials to be found on line, here is the official Oracle documentation:
\nhttp:\/\/docs.oracle.com\/javaee\/6\/tutorial\/doc\/gipzz.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

As mentioned in my last post, the XCRI-CAP project has allowed us to use many of the new features of Java EE 6. One of the new features we’ve been able to implement is the RESTful web service support via JAX-RS.\u00a0 Previously we have implemented JAX-WS web services by turning EJB Session beans into web […]<\/p>\n","protected":false},"author":34,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[169],"tags":[201,202,200,203,204],"_links":{"self":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts\/63"}],"collection":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/users\/34"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/comments?post=63"}],"version-history":[{"count":4,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts\/63\/revisions"}],"predecessor-version":[{"id":67,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts\/63\/revisions\/67"}],"wp:attachment":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/media?parent=63"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/categories?post=63"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/tags?post=63"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}