Truck Rental Java Implementation


At this point, from the analysis of the requirements, the initial design has been created. After reviewing the design to ensure that it addresses all the requirements, you can now focus on coding the application in Java. The Together ControlCenter generates source code for each class that appears in a class diagram. The design for the Truck Rental example generated the following 10 classes:

  • RentalServlet

  • RSClientClass

  • RentalSession

  • RentalSessionBean

  • RentalSessionHome

  • REClientClass

  • RentalEntity

  • RentalEntityBean

  • RentalEntityHome

  • RentalEntityPK

The RentalEntity and RentalSession are the remote interfaces. RentalEntityHome and RentalSessionHome are the home interfaces. RentalEntityPK is the primary key for the entity bean. You should not manually edit any of these support files if they were generated by the Together ControlCenter.

The REClientClass and RSClientClass encapsulate the Home and Remote interfaces for the corresponding RemoteEntity and RemoteSession respectively. These client links are the proxy for the bean. You will add operations to the client classes to forward the message to the bean.

As you create the class diagrams with Together ControlCenter, it dynamically generates Java source code. The final transition to J2EE is to edit the generated source files, where indicated with comments and add the necessary import statements.



BEA WebLogic Platform 7
BEA WebLogic Platform 7
ISBN: 0789727129
EAN: 2147483647
Year: 2003
Pages: 360

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net