You should see the following output:

Aug 18, 2014 8:57:07 PM org.apache.cxf.common.jaxb.JAXBUtils logGeneratedClassNames
INFO: Created classes: generated.Invoice, generated.ObjectFactory

The following Java source files generated at the location set by the –d parameter and –p gives the package structure:

rest/invoice/v1/InvoiceserviceV1Resource
rest/invoice/v1/InvoiceserviceV1ResourceImpl
rest/invoice/v1/Invoice
rest/invoice/v1/ObjectFactory
rest/invoice/v1/Service

Open the TestCase and edit the TestStep created in step 2.

Add an invoice ID to the TestSteps's request, for example, 12345.

Running the TestCase should result in all the TestStep's Assertions failing, and a response with HTTP status 204 no content under the Raw tab. This is expected since we have no implementation yet.

First implement InvoiceserviceV1ResourceImpl.java with the following code:

package rest.invoice.v1;

public class InvoiceserviceV1ResourceImpl implements InvoiceserviceV1Resource {

  public Invoice getInvoiceid(String id) {
    ObjectFactory objectFactory = new ObjectFactory();
    Invoice invoice = objectFactory.createInvoice();
    if (id != null && id.equals("12345")) {
      invoice.setId("12345");
      invoice.setCompanyName("Test Company");
      invoice.setAmount(100.0d);
    }
    return invoice;
  }

}

Next, add the annotation @XmlRootElement(name = "Invoice"); otherwise, marshaling from the JavaBean to the response JSON doesn't work:

@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "invoice", propOrder = {
    "id",
    "companyName",
    "amount"
})
@XmlRootElement(name = "Invoice")
public class Invoice {
…

Add an import statement for the annotation to the top of Invoice.java:

import javax.xml.bind.annotation.XmlRootElement;

Finally, delete the package-info.java class; otherwise, there will be a namespace prefix on the JSON response.

Invoice.java: This is a JavaBean representation of the invoice XML content. This class has binding annotations to allow the Apache CXF JAX-RS implementation to marshal invoice objects to XML content and unmarshal XML content to invoice objects:

@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "invoice", propOrder = {
    "id",
    "companyName",
    "amount"
})
@XmlRootElement(name = "Invoice")

ObjectFactory.java: This class can optionally be used to create instances of the Invoice.java class by calling the createInvoice() factory method. There is also a factory method JAXBElement<Invoice> createInvoice(Invoice value) to create JAXB invoice XML bindings. These factory methods can be useful to separate object creation code from your service methods when dealing with more complicated schema examples, but they are not especially useful in our case.

InvoiceserviceV1Resource.java:This is a JAX-RS annotated Java interface to represent the RESTful invoice service and its resource. In this example, we have the following code:

@Path("/invoiceservice/v1/")
public interface InvoiceserviceV1Resource {

    @GET
    @Produces("application/json")
    @Path("/invoice/{id}")
    Invoice getInvoiceid(@PathParam("id") String id);
}

The annotations are used by the Apache CXF JAX-RS implementation to map HTTP requests to matching Java methods. In this case, implementations of this interface that is InvoiceserviceV1ResourceImpl will invoke the getInvoiceid(…) method passing in the {id} path parameter as the String id variable if there is a HTTP GET request to the resource /invoiceservice/v1/invoice/{id}. Other annotated service methods to support POST, PUT and DELETE requests could also be added here and in the implementation. See <chapter 1 samples>/rest/invoice_crud/src/main/java/rest/invoice/crud/v1/InvoiceServiceCRUDV1Resource.java for an example like this.

InvoiceserviceV1ResourceImpl.java: This is the implementation of the preceding interface to provide the Java code to run when a matching request is made. We added code to the Invoice getInvoiceId(String id) of this class so that if the invoice (id) is 12345, then we a create a new Invoice object using the ObjectFactory, populate it with the expected values, and return it in the response. In the background, Apache CXF is able to marshal this into JSON content before dispatching the response back to SoapUI. Unlike the JAX-WS example in the first recipe, there was no holder object, so we were responsible for creating the Invoice object ourselves.

Service.java: This is a server class that publishes our stub service's implementation. Like in the first recipe's JAX-WS server code, the endpoint and service timeout can be set here.