This is
submitted to a special (again, sort of!) servlet that validates the information using the
configuration in tomcat-users.xml. Assuming the information is valid, the container then
returns the resource that was originally requested, loginOk.jsp, and the user is then effectively
logged in. If the information is not valid, the container redirects to the page specified by
the
element, which in our case is simply the login.jsp again, but where a
message will be displayed in red saying the information was invalid (note the query string on
the value of the ??”that is a flag that tells the JSP to display the message).
Now all the pieces of the puzzle should fit into place in your mind. All except for one, that
is: this all explains how logins occur, which is something the application needs, of course, but
how does it constrain the DWR-remotable classes and methods? The answer is to be found in
the dwr.xml file, and that??™s where we??™re headed next.
dwr.xml
We??™ve already seen the DWR configuration file a few times now, so most of this should be old
hat to you by now. In Listing 5-5, you can see the configuration file.
Listing 5-5. The DWR Configuration File, dwr.
Pages:
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381