Conextions' Expresso works in a similar manner. As with Stingray, a developer begins by simply navigating through the app's screens. With the model in place, the developer has two routes for deployment on the Web. For example, the developer can build a JavaBean that encapsulates the actions needed to update a client's balance. The second route lets the developer treat the entire legacy app as a relational database.
Screens appear on the client side as a table.
To pass input to the legacy app, the client code simply executes a JDBC function to perform an update or insert. The Java app reads the results by fetching from the database. When the Web app is built and deployed, regardless of which route the developer takes, the legacy app won't notice anything unusual. It's as if the Expresso Server includes a fast typist sitting at a 3270 screen, taking requests from the Java client and sending the results back. In addition, the Expresso Server can service multiple back-end legacy apps simultaneously.