Note: In NetBeans IDE 6.5, you can generate entity classes and RESTful web services in a single wizard. Instead of choosing New > Entity Classes from Database, choose New > Web Services > RESTful Web Services from Database. Follow the same steps described in the rest of this procedure and in Generating RESTful Web Services from Entity Classes. The Generated Classes step of the New Entity Classes from Database wizard corresponds to Step 3 of Generating RESTful Web Services from Entity Classes. However, if you generate entity classes and RESTful web services separately, as described in this tutorial, you can see in greater detail how the process works.

Note: On Tomcat, this data source may not exist. In this case, choose New Data Source from the Data Source drop-down field. The Create Data Source dialog opens. Type jdbc/sample in the JNDI Name field. From the Database Connection drop-down field, select jdbc:derby://hostname:1527/sample [app on APP]. Click OK. The dialog closes and you return to the Database Tables panel. See also the RESTful Service on Tomcat tutorial for NetBeans IDE 6.0.

Under Available Tables, select CUSTOMER and then click Add. The DISCOUNT_CODE table, which has a relationship with the CUSTOMER table, is automatically added to the Selected Tables list too. You now see the following:

Click Next.

Under Package, type customerdb. You now see the following.

Click Create Persistence Unit. The following dialog appears.

Click Create. You return to the Entity Classes pane. Click Finish, and the IDE creates the entity classes.

Note: In this tutorial, you skip the optional Mapping Options pane, which lets you change the default annotations used for mapping collections.

Look in the Projects window. You now see the following.

In the Resource Package field, type customerdb.service, and in the Converter Package field, type customerdb.converter. Accept all other default settings, as shown below:

Here you can see everything that the IDE will generate for you. The IDE uses the container-item pattern to generate the resource classes. For example, for the Customer entity class, the IDE generates a container resource called CustomersResource and an item resource called CustomerResource. Also, for each resource class, the IDE generates a converter class used for generating the resource representation from the corresponding entity instance, such as CustomersConverter and CustomerConverter. Furthermore, there is an additional converter class called reference converter, such as CustomerRefConverter, for representing relationships.

Click Finish.

Look in the Projects window. You now see the following:

The RESTful Web Services node in the Projects window displays all the RESTful web services in your project. The value between the square brackets, such as [/customers/], is the value for the URI template. You can also navigate to the source file by doubling clicking on this node. This view also displays all the HTTP methods and Sub-resource locator methods. Again, you can navigate to the methods by double clicking on the nodes.

If the output window shows an error message that one or more classes fails to exist and the project does not build, add the Jersey libraries to the compile-time libraries. Right-click the project node and select Properties. In the Properties tree menu, select Libraries. Click Add Library and browse for the Jersey libraries.

On the left-hand side is the set of root resources. Here they are named customers and discountCodes.

Click the customers node. The browser window shows you a list of parameters for testing the Customers service.

You can set the following parameters:

Click on the Methods drop-down list to select GET(application/xml). Type "3" in the Max field. Leave default values in the other parameters and click Test. The result is displayed in the Test Output section.

There are 4 tabs in the Test Output section.

Note that you have 6 results listed although you specified a maximum of 3 entities to display. Open the Raw View tab to see the reason why. Each entity corresponds to a <customer> element, and you have only 3 customers in the test results. However, the Tablular view lists URIs, not entities, and each entity has two URIs, one as an attribute of the parent <customer> element and one as an attribute of the child <discountCode> element. So although there are only 3 customer entities, there are 6 URIs in total.

@GET
@Produces("text/html")
public String getGoogleMap() {
// Drag and drop the getGoogleMap operation here

   return "";
}

In the IDE, open the Services tab and expand the Web Services node. Under Web Services, expand Google. Under Google, expand Map Service.

The IDE adds the following try block to the getGoogleMap method in the CustomerResource class.

@GET
@Produces("text/html")
public String getGoogleMap() {
// Drag and drop the getGoogleMap operation here

    try {

         String address = "16 Network Circle, Menlo Park";
         java.lang.Integer zoom = 15;
         String iframe = "false";
         RestResponse result = GoogleMapService.getGoogleMap(address, zoom, iframe);
         //TODO - Uncomment the print Statement below to print result.
         //System.out.println("The SaasService returned: "+result.getDataAsString());
    } catch (Exception ex) {
         ex.printStackTrace();
    }

    return "";

}
        

The IDE also creates the packages org.netbeans.saas and org.netbeans.saas.google, which contain the following classes and resources:

@GET
@Produces("text/html")
public String getGoogleMap() {
// Drag and drop the getGoogleMap operation here

    try {

         String address = "16 Network Circle, Menlo Park";
         java.lang.Integer zoom = 15;
         String iframe = "false";
         RestResponse result = GoogleMapService.getGoogleMap(address, zoom, iframe);
         return result.getDataAsString();
    } catch (Exception ex) {
         ex.printStackTrace();
    }

    return "";

        }

From the table, click customer1. A test window for that customer opens in the main pane. From the drop-down menu, select the text/html MIME type. Click Test. The GoogleMap of 16 Network Circle, Menlo Park opens in the Raw View.

@GET
@Produces("text/html")
public String getGoogleMap() {
    try {
         Customer c = getEntity();
         String address = c.getAddressline1() + " " + c.getAddressline2() + " " +
                 c.getCity() + " " + c.getState() + " " + c.getZip();
         java.lang.Integer zoom = 15;
         String iframe = "false";

         RestResponse result = GoogleMapService.getGoogleMap(address, zoom, iframe);
         return result.getDataAsString();

     } catch (Exception ex) {
         ex.printStackTrace();
     }

     //The close() method is only necessary with versions of NetBeans IDE earlier than 6.5

         finally {
             PersistenceService.getInstance().close();
     }
     return "";
            }

Test the RESTful web services again. Again, select the text/html MIME type for one of the customers. A Google map of that customer's address in the database now displays in the Raw View. For customer1, the following map displays:

Note: If GoogleMaps cannot find an address, it shows a zoomed in view of the ocean.