This topic outlines changes made to the page flow features in WebLogic Workshop
releases. For more details, see the latest WebLogic Workshop Release Notes
on the BEA E-docs web site.
Changes from WebLogic Workshop 8.1 to 8.1 SP2
This section summarizes the changes in the WebLogic Workshop 8.1 Service
Pack 2 (SP2) release. The prior release was WebLogic Workshop 8.1.
-
-
In @jpf:forward annotations, the return-to="action"
attribute was renamed as return-to="previousAction",
to clarify the purpose of this attribute. After installing SP2, when you
access an existing page flow in the IDE, WebLogic Workshop prompts you about
the deprecated return-to="action"
attributes. If you select the Yes button, the update is made for you automatically.
-
In @jpf:forward annotations, the return-to="page"
attribute was renamed as return-to="previousPage",
to clarify the purpose of this attribute. After installing SP2, when you
access each existing page flow in the IDE, WebLogic Workshop prompts you
to about the deprecated return-to="page"
attributes. If you select the Yes button, the update is made for you automatically.
-
In @jpf:forward annotations, SP2 added support for the
return-to="currentPage"
attribute. For information about the @jpf:forward annotation, see
@jpf:forward
Annotation.
- SP2 supports a more flexible forward validation process. Instead of using
an @jpf:action annotation with an attribute such as validation-error-page="formPage.jsp",
SP2 provides a new annotation: @jpf:validation-error-forward. For information,
see @jpf:validation-error-forward
Annotation.
-
After installing SP2, WebLogic Workshop changes any "return-to-page:
IDs" and "return-to-action: IDs"
entries in the @jpf:view-properties XML to "return-to:
IDs". This change happens automatically the first time you open
an existing page flow controller class file in the IDE.
-
In a web project that uses page flows, WebLogic Workshop prompts you
to move each page flow's WEB-INF/jpf-struts-config-*.xml file to a new,
recommended location:
WEB-INF/.pageflow-struts-generated/jpf-struts-config-*.xml
This recommended change was designed to help you understand that these
jpf-struts-config-*.xml XML files are generated files, and therefore do
not need to be maintained in a source file management system along with
your application's source files. However, you have the option of entering
No in response to the prompt. You may want to delay the migration, for example,
if currently you do maintain these generated XML files in a source file
management system.
-
Several new NetUI tags were added in SP2:
-
The .<pageflow>.lyt file evolved into a @jpf:view-properties annotation
that described the page flow's Flow View layout structure
-
The @jpf:nestable was replaced by the @jpf:controller nested="true"
annotation on the page flow's main class
-
@jpf:exceptionHandler -> @jpf:exception-handler (on methods)
-
loginRequired (attribute on @jpf:action) -> login-required
-
validationErrorPage (attribute on @jpf:action) -> validation-error-page
-
returnAction (attribute on @jpf:forward) -> return-action
-
returnTo (attribute on @jpf:forward) -> return-to
-
returnFormType (attribute on @jpf:forward) -> return-form-type
-
returnForm (attribute on @jpf:forward) -> return-form
-
messageKey (attribute on @jpf:catch) -> message-key