If you're using JSR 303 annotations that are not supported by Spring Roo, you'll need to create custom setter methods (defined in *_Roo_DataOnDemand.aj) for setting persistent entity field values. The following listing shows some of the setter methods (setNumOfSeats and setOrigin) auto-generated by Roo for the Flight entity; the following is the FlightDataOnDemand_Roo_DataOnDemand.aj method:

public Flight FlightDataOnDemand.getNewTransientFlight
(int index) {
  sample.roo.flightapp.domain.Flight obj = new 
                  sample.roo.flightapp.domain.Flight();
  setEmbeddedId(obj, index);
  setNumOfSeats(obj, index);
  setOrigin(obj, index);
  setDestination(obj, index);
  ...
  return obj;
}

private void FlightDataOnDemand.setEmbeddedId(Flight obj, 
 int index) {
  java.lang.String flightId = "flightId_" + index;
  ...
  obj.setId(embeddedIdClass);
}

private void FlightDataOnDemand.setNumOfSeats(Flight obj, 
 int index) {
  java.lang.Integer numOfSeats = new Integer(index);
  obj.setNumOfSeats(numOfSeats);
}

private void FlightDataOnDemand.setOrigin(Flight obj, 
 int index) {
  java.lang.String origin = "origin_" + index;
  if (origin.length() > 20) {
    origin = origin.substring(0, 20);
  }
  obj.setOrigin(origin);
}
...

In the code listing, there are a couple of things to notice about the Flight entity that is created:

To address the issue with JSR 303 support in the auto-generated Flight entity instance by FlightDataOnDemand_Roo_DataOnDemand.aj, we can write custom setNumOfSeats, setOrigin, and setDestination methods in the FlightDataOnDemand.java class, which does the following:

It is important to note that if you create setNumOfSeats, setOrigin, and setDestination methods in the FlightDataOnDemand.java class, then Roo removes these methods from the corresponding FlightDataOnDemand_Roo_DataOnDemand.aj AspectJ ITD. This requires that the signature of methods in the FlightDataOnDemand.java class is the same as the signature of methods defined in the corresponding FlightDataOnDemand_Roo_DataOnDemand.aj AspectJ ITD file. Similarly, you can customize any method of FlightDataOnDemand_Roo_DataOnDemand.aj by writing them in the FlightDataOnDemand.java class.

The following figure shows how Roo removes setNumOfSeats, setOrigin, and setDestination methods from the FlightDataOnDemand_Roo_DataOnDemand.aj file:

The figure shows that Spring Roo Shell monitors the FlightDataOnDemand.java class (because it is annotated with Roo's @RooDataOnDemand annotation). When any change is made to the FlightDataOnDemand.java class, Roo triggers add-on(s) responsible for managing the AspectJ ITD file(s) corresponding to the FlightDataOnDemand.java class. In the case of FlightDataOnDemand, Roo triggers Dod add-on ('data on demand') to update FlightDataOnDemand_Roo_DataOnDemand.aj AspectJ ITD, so that the AspectJ ITD is in sync with the FlightDataOnDemand.java class. When you add setNumOfSeats, setOrigin, and setDestination methods in the FlightDataOnDemand.java class, Dod add-on checks if the methods already exist there. If they exist, Dod add-on removes those methods from the FlightDataOnDemand_Roo_DataOnDemand.aj AspectJ ITD.

It is important to note that modifying a Java class that is annotated with Roo annotations may result in multiple AspectJ ITDs getting affected. For instance, if you remove the modifiedBy field from the Flight.java class, Roo will update the Flight_Roo_JavaBean.aj, Flight_Roo_ToString.aj, and FlightDataOnDemand_Roo_DataOnDemand.aj AspectJ ITD files to reflect the removal of the modifiedBy field.

We mentioned earlier that the @RooIntegrationTest annotation in *IntegrationTest.java defines attributes which let you control the integration test methods that are auto-generated by Roo in the *_Roo_IntegrationTest.aj AspectJ ITD file. The @RooIntegrationTest annotation defines the following attributes to control the auto-generation of integration test methods: count, find, findAll, findAllMaximum, findEntries, flush, merge, persist, and remove. If the value of any of these attributes is specified as false, then the corresponding test method is removed from the *_Roo_IntegrationTest.aj AspectJ ITD file. For instance, the testFindAllFlights method searches for all Flight instances in the database, which may not be desirable for performance reasons. To instruct Spring Roo to remove the auto-generated testFindAllFlights method from the FlightIntegrationTest_Roo_IntegrationTest.aj file, all you need to do is to specify the value of the findAll attribute value as false in the @RooIntegrationTest annotation, as shown here:

@RooIntegrationTest(entity = Flight.class, findAll=false)
public class FlightIntegrationTest {
   ...
}

In this recipe we saw how to create integration tests using the test integration command. You can also use the testAutomatically argument of the entity command to instruct Roo to create integration tests at the time of entity creation, as shown here:

roo> entity --class ~.domain.Flight --testAutomatically --identifierType ~.domain.FlightKey --table FLIGHT_TBL

As with the 'data on demand' class, you can provide a custom implementation for an integration test method in your *IntegrationTest.java class. For instance, if you want to modify the testPersist Roo-generated test method with a customized testPersist method, create a testPersist method in the FlightIntegrationTest.java file. Adding the testPersist method to *IntegrationTest.java results in the removal of the testPersist method from the corresponding *_Roo_IntegrationTest.aj file by Roo. Similarly, you can customize any other test method defined in the *_Roo_IntegrationTest.aj file.