Realizing nodes in Web diagrams

Realizing nodes in Web diagrams

When a node in a Web diagram is realized, the underlying resource represented by the node comes into existence.

To realize an unrealized node, either double-click the node (to invoke the appropriate wizard) or change its path to refer to an existing resource.
The following table describes the action that results from double-clicking:

Object Action that results from double-clicking
JSP The JSP wizard opens. See Creating JavaServer Pages (JSP) files.
Note: Do not select a template from sample page templates, because this produces a JSP file with the Struts tags removed. Instead of samples, select a user-defined page template that you created. To create a page template, create a Struts JSP file and save it as page template from the menu Page Designer's File > Save As Page Template.
HTML page The HTML wizard opens. Through this wizard you can create the HTML page. The HTML page wizard automatically opens the JSP editor on the new HTML page, and the visual representation of the HTML page changes to represent a realized HTML page.
Action mapping If the action mapping does not exist, the Action Mapping wizard opens. If the action mapping exists but is not configured, a configuration dialog box opens. The former case is the default. In the latter case the dialog box lists all the Struts configuration files that are defined for the Struts application (via the web.xml file). The Struts configuration file editor opens, and a new action mapping entry is generated and selected. You can change the default behavior by setting Web diagram preferences.
Web application The Web Project wizard opens.
Java bean part The New Java Class wizard opens.
Form bean If the form bean does not exist, by default the New ActionForm Class wizard opens. If the form bean exists but is not defined in a configuration file, a configuration dialog box opens, and the dialog box lists all the Struts configuration files that are defined in the web.xml file for the Struts application. The Struts configuration file editor is opened on the chosen configuration file, and a new form bean entry is generated and selected. You can change the default behavior by setting Web diagram preferences.
Module If the module does not exist, the Module wizard opens. If the module exists but the entry point action mapping does not exist, the Action Mapping wizard opens.

You can also realize an unrealized part by modifying its properties to identify it as an existing part. For example, an action mapping part can be made realized by changing its path to be the path of an existing action mapping. Changing the path of an action mapping or Web page part can be done by either selecting the part and changing the attribute on the properties page, or by double-clicking on the node's label, or by bringing up the pop-up menu of the part (right mouse clicking over the part) and selecting the Rename action. An unrealized connection that represents an action mapping forward can be realized in a way similar to the way described above. The difference being that the pop-up menu option is Edit the forward name.

Related concepts
Web diagrams and the Web diagram editor

Related tasks
Creating Web diagrams for new applications
Editing Web diagrams - overview
Creating JavaServer Pages (JSP) files
Realizing connections in Web diagrams
Setting preferences for Web diagrams

Related reference
Web diagram editor: pop-up menu
Resolution rules for realizing Web diagram parts
Preferences for the Web diagram editor

Object	Action that results from double-clicking
JSP	The JSP wizard opens. See Creating JavaServer Pages (JSP) files. Note: Do not select a template from sample page templates, because this produces a JSP file with the Struts tags removed. Instead of samples, select a user-defined page template that you created. To create a page template, create a Struts JSP file and save it as page template from the menu Page Designer's File > Save As Page Template.
HTML page	The HTML wizard opens. Through this wizard you can create the HTML page. The HTML page wizard automatically opens the JSP editor on the new HTML page, and the visual representation of the HTML page changes to represent a realized HTML page.
Action mapping	If the action mapping does not exist, the Action Mapping wizard opens. If the action mapping exists but is not configured, a configuration dialog box opens. The former case is the default. In the latter case the dialog box lists all the Struts configuration files that are defined for the Struts application (via the web.xml file). The Struts configuration file editor opens, and a new action mapping entry is generated and selected. You can change the default behavior by setting Web diagram preferences.
Web application	The Web Project wizard opens.
Java bean part	The New Java Class wizard opens.
Form bean	If the form bean does not exist, by default the New ActionForm Class wizard opens. If the form bean exists but is not defined in a configuration file, a configuration dialog box opens, and the dialog box lists all the Struts configuration files that are defined in the web.xml file for the Struts application. The Struts configuration file editor is opened on the chosen configuration file, and a new form bean entry is generated and selected. You can change the default behavior by setting Web diagram preferences.
Module	If the module does not exist, the Module wizard opens. If the module exists but the entry point action mapping does not exist, the Action Mapping wizard opens.