IN THIS CHAPTER

In the last chapter we gave our user interface strategy a final review and then traced the communication from front to back as a means to solidify our architecture via a sequence diagram. This chapter focuses on pulling together the various technology puzzle pieces we have presented over the last three chapters and building the first round of our architectural prototype.

This portion of the Remulak solution will present both simple inquiry and update pathways through the Maintain Relationships use-case. The architecture will consist of Apache Tomcat as the servlet/JSP container and JavaBeans as the implementation for the entity classes. The JSPs will be identical between the two implementations, and the servlets will require only ...

Get Developing Applications with Java™ and UML now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.