JATO tag info?
I am having a hard time finding out how some of the event flows take place
in the JSP's to beans. As far as I see it, by looking at an outputted
project of the migration tool (deploy), I see a series of jsp's...let's say
one is called Login.jsp.
The header header had an include with some jsp declarations like "page" and
"taglib"....then there is the following
<jsp:useBean id="viewBean" class="example.example.LoginViewbean"
scope="request"...etc
Now in this login page there is a form to submit your username and password.
WHEN one hits the SUBMIT button inside of the ><Jato: form> tag...WHERE DOES
THAT INPUTTED DATA GO?There is no action attribute on this tag? Does it
go to the LoginViewBean..? Then does that call the master servlet of the
example project?
Eric Hagopian
Bank of America
<a href="/group/SunONE-JATO/post?protectID=070212020098035125169242065176231253000 098083009039175188023077067046010218229239098201196026">eric.hagopian@b...< ;/a>
312.974.6411
[1136 byte] By [
Guest] at [2007-11-25 9:30:15]
Eric--
> So the page info that the page sends to the viewBean contains
> <page> <display fields>
> <event>
>
> Login Submit button,name textbox, password textbox ?
Basically, all the form's field values are submitted back to the servlet,
where they are then "distributed" to the corresponding display fields on the
target page and its subviews. In addition to the form fields, there are
also "page" and "pageAttributes" request parameters. The request handler
event to ultimately call is derived from the set of request parameters.
> What event gets fired? Just the request itself?
As far as events go, understand that there are two different phases: the
submit cycle, and the display cycle. During the submit cycle, which is what
we're talking about, the servlet fires several request-level events:
checkBeanName (if checking enabled)
onNewSession (if it's a new session)
onSessionTimeout (if the session has timed out)
onBeforeRequest
onBeforeHeader
initializeRequestContext
handle<child name>Request (request event handler on the view)
...
<display cycle takes place here>
...
onBeforeSessionUpdate
onAfterRequest
See the processRequest(...) method in ApplicationServletBase.java (starting
at line 320) for the real skinny.
Todd
--
Todd Fast
Senior Engineer
Sun/Netscape Alliance
<a href="/group/SunONE-JATO/post?protectID=189233080150035131169232031248130090006 048031198039130252055210">todd.fast@e...</a>
Guest at 2007-7-1 16:36:46 >
Two embedded comments
> Basically, all the form's field values are submitted back to the
servlet,
> where they are then "distributed" to the corresponding display
fields on the
> target page and its subviews.
Todd has described the mapping of ServletRequest parameters (see
ServletRequest.getParameter(java.lang.String name) to JATO display
field/model values. This mapping is implicitly handled by the JATO
application framework in order to provide the developer with the
convenience and power of the displayField/model field programming
model.
But ... this implicit mapping does not preclude the developer from
directly using the ServletRequest.getParameter(java.lang.String name)
API, or any of the javax.servlet API for that matter (e.g.
ServletRequest, ServletResponse, etc). Roughly speaking ND developers
who are working in JATO can think of the JATO DisplayField.getValue()
as an analog of the ND's CSpDisplayField.getValue(), while
ServletRequest.getParameter(java.lang.String name) is the analog for
CSpider.getWebVarjava.lang.String name).
Please remember that the JATO framework is designed to add power and
convenience while still allowing full use of the standard J2EE API's.
> > What event gets fired? Just the request itself?
>
> As far as events go, understand that there are two different
phases: the
> submit cycle, and the display cycle. During the submit cycle,
which is what
> we're talking about, the servlet fires several request-level events:
>
> checkBeanName (if checking enabled)
> onNewSession (if it's a new session)
> onSessionTimeout (if the session has timed out)
> onBeforeRequest
> onBeforeHeader
> initializeRequestContext
> handle<child name>Request (request event handler on the view)
> ...
> <display cycle takes place here>
> ...
> onBeforeSessionUpdate
> onAfterRequest
>
> See the processRequest(...) method in ApplicationServletBase.java
(starting
> at line 320) for the real skinny.
>
> Todd
>
> --
> Todd Fast
> Senior Engineer
> Sun/Netscape Alliance
> <a href="/group/SunONE-JATO/post?protectID=189233080150035131169232031248130208071 048">todd.fast@e...</a>
Guest at 2007-7-1 16:36:46 >
Two embedded comments
> Basically, all the form's field values are submitted back to the
servlet,
> where they are then "distributed" to the corresponding display
fields on the
> target page and its subviews.
Todd has described the mapping of ServletRequest parameters (see
ServletRequest.getParameter(java.lang.String name) to JATO display
field/model values. This mapping is implicitly handled by the JATO
application framework in order to provide the developer with the
convenience and power of the displayField/model field programming
model.
But ... this implicit mapping does not preclude the developer from
directly using the ServletRequest.getParameter(java.lang.String name)
API, or any of the javax.servlet API for that matter (e.g.
ServletRequest, ServletResponse, etc). Roughly speaking ND developers
who are working in JATO can think of the JATO DisplayField.getValue()
as an analog of the ND's CSpDisplayField.getValue(), while
ServletRequest.getParameter(java.lang.String name) is the analog for
CSpider.getWebVarjava.lang.String name).
Please remember that the JATO framework is designed to add power and
convenience while still allowing full use of the standard J2EE API's.
> > What event gets fired? Just the request itself?
>
> As far as events go, understand that there are two different
phases: the
> submit cycle, and the display cycle. During the submit cycle,
which is what
> we're talking about, the servlet fires several request-level events:
>
> checkBeanName (if checking enabled)
> onNewSession (if it's a new session)
> onSessionTimeout (if the session has timed out)
> onBeforeRequest
> onBeforeHeader
> initializeRequestContext
> handle<child name>Request (request event handler on the view)
> ...
> <display cycle takes place here>
> ...
> onBeforeSessionUpdate
> onAfterRequest
>
> See the processRequest(...) method in ApplicationServletBase.java
(starting
> at line 320) for the real skinny.
>
> Todd
>
> --
> Todd Fast
> Senior Engineer
> Sun/Netscape Alliance
> <a href="/group/SunONE-JATO/post?protectID=189233080150035131169232031248130208071 048">todd.fast@e...</a>
Guest at 2007-7-1 16:36:46 >
