이 콘텐츠는 선택한 언어로 제공되지 않습니다.
7.3. Page parameters
A Faces request (a JSF form submission) encapsulates both an action (a method binding) and parameters (input value bindings). A page action can also require parameters.
Since non-Faces (GET) requests can be bookmarked, page parameters are passed as human-readable request parameters.
You can use page parameters with or without an action method.
7.3.1. Mapping request parameters to the model 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
Seam lets us provide a value binding that maps a named request parameter to an attribute of a model object.
The
<param>
declaration is bidirectional, as with value bindings for JSF input:
- When a non-Faces (GET) request for the view ID occurs, Seam sets the value of the named request parameter to the model object, after performing appropriate type conversions.
- Any
<s:link>
or<s:button>
includes the request parameter transparently. The parameter value is determined by evaluating the value binding during the render phase (when the<s:link>
is rendered). - Any navigation rule with a
<redirect/>
to the view ID includes the request parameter transparently. The parameter value is determined by evaluating the value binding at the end of the invoke application phase. - The value is transparently propagated with any JSF form submission for the page with the given view ID. This means that view parameters behave like
PAGE
-scoped context variables for Faces requests.
However we arrive at
/hello.jsp
, the value of the model attribute referenced in the value binding is held in memory, without the need for a conversation (or other server-side state).