IN THIS CHAPTER
The model is the least tightly defined piece of the Struts MVC architecture, and for good reason. Models, by definition, are used to control access to the tangled world of business logic—all the stuff that isn’t display or control flow, but comprises the actual mechanisms of what happens underneath.
Because of this, the model can be composed of just about anything at all. For example, it may be made up of any or all of the following:
A JDOM parser talking to an XML file
A JNDI implementation communicating with an LDAP server
An EJB stub communicating to an EJB server
A SOAP client communicating with a remote Web service ...