The Java BluePrints, for example, originally recommended using EJBs to encapsulate the MVC Model.
ColdFusion and Active Server Pages are examples of contemporary technologies that also implemented this model.
All of the logic was separated out into a servlet, leaving the JSP with the sole responsibility of rendering the output for the content provided.
In December 1999, JavaWorld published an article by Govind Seshadri entitled Understanding JavaServer Pages Model 2 architecture.
The "Model" part of the MVC architecture was left open by Govind, with a suggestion that nearly any data-structure could meet the requirements.
This project formalized the division between View and Controller and claimed implementation of the "Model 2" pattern.
[3] Once again, the implementation of the "Model" was left undefined with the expectation that software developers would fill in an appropriate solution.
More recently, Hibernate, iBatis, and Object Relational Bridge were listed as more modern options that could be used for a model.