,ch14.9433 Page 481 Monday, February 14, 2005 12:55 PM
In a STXX application, your action form holds XML data. STXX provides two spe
cialized classes that wrap XML data in an
. The contained XML can be
represented as a traditional DOM object using the
or as a JDOM object
. JDOM provides a more natural API than DOM, so the
used in this recipe.
element references an XML model that describes the XML structure
of the form data. The XML models for your application are defined in the WEB INF/
xmlform models.xml file. Example 14 32 shows the model, representing user infor
mation, used in this recipe.
Example 14 32. XML models used by STXX
A custom action in STXX performs the same functions as in a conventional Struts
application: you retrieve data from the form, access the model, and forward to a des
tination. For STXX, the pattern can be specifically laid out as follows:
1. Retrieve the
and extract the form data as a DOM or JDOM object.
2. Access the business model to retrieve data.
3. Format the data into an XML in memory representation.
4. Forward the request to a STXX transformation pipeline.
The actions defined in Example 14 31 represent a typical flow common to most web
applications. The first action, /viewUserList, displays data on a page. The second
action, /addUser, presents a form where a user can input data. The third action,
/saveUser, saves the data in the model and forwards back to the first action.
Here's the first action mapping:
, shown in Example 14 33, retrieves data stored in application
scope and builds a JDOM document from it. The action saves the document in the
request and forwards to success.
Integrating Struts and XSLT | 481
This is the Title of the Book, eMatter Edition
Copyright 2005 O'Reilly & Associates, Inc. All rights reserved.