While the booking tutorial does not take advantage of windowScope, it is clear that functionality is reduced. Request map cleared prematurely.2) NPE trying to rewrite a null viewID into the document:Īt .DOMUtils.isWhitespaceText(DOMUtils.java:394)Īt .DOMUtils.printNode(DOMUtils.java:351)Īt .DOMUtils.printNode(DOMUtils.java:355) Side effects of this problem are the following symptoms:ġ) Console messages of the following form: Spring webflow applications, by default, use a POST->Redirect->GET pattern for navigation, but during the subsequent GET operation, the Spring lifecycle implementation does not appear to be executing the phase listeners during the RESTORE_VIEW phase. The ICEfaces BridgeSetup class uses a JSF PhaseListener to restore certain scope variables into the request map. There is an issue with the Spring implementation of the Lifecycle that affects the operation of ICEfaces. This tutorial borrows heavily from the Spring Web Flow sample booking application. Authenticated users can also review their bookings. Users can search for hotels and, after authenticating, book a room. The simple business case for this tutorial is the Spring Web Flow standard "booking application". Additional libraries are needed to support these frameworks and have been listed as dependencies in the tutorial's pom.xml file. This tutorial uses Spring Web Flow 2.5, Spring Security 5.1, Spring Core 5.1, JSF 2.2.16 and ICEfaces 3.3.0_P07. Understanding how the various parts of the web.xml file are organized to accomodate both frameworks is essential to understanding this tutorial and being able to extend it to meet your own requirements. Both technologies leverage the Servlet API. The purpose of this tutorial is to demonstrate how application developers can use both Spring Webflow 2.5 and ICEfaces 3.3.0 in the same application. This tutorial borrows heavily on existing JSF tutorials for Spring Web Flow, and is an evolution of the tutorial for integrating ICEfaces 3.x with Spring Web Flow 2.3.1. Go directly to the portion of this tutorial dealing with Spring Security 5.1 configuration. Authorization is applied at either the web resource level using Servlet Filters and/or at the business/service method level using aspects and annotations. Authentication is possible against any number of repositories and databases. Spring Security 5.1 provides an API for configuring authentication and authorization. Spring Web Flow is a library that extends Spring MVC to user defined "controllers using a domain-specific-language." Web Flow is appropriately used when several actions need to be performed in order for a greater action to be performed (booking a hotel, or a flight for instance). The Firefox error console (in 3.0.7+) does not show any messages.Spring Web Flow 2.5, Spring Security 5.1, and ICEfaces 3.3 In the failing case the error console says "Network - file://localhost/C:/TEMP/bugtest/uploadComplete.html The loading of the URL has been blocked for security reasons." AND it fails even if you fully qualify the action URL in the javascript. This test is quite a bit simpler than bug 484857 - it requires only a single html page (plus the target of the action=, to see if the action is taken).īTW, regarding the Opera response, I found there's a twist - the test case works if served by a webserver, but fails if you open the page from disk. If you change the failing case to have an action with a fully qualified URL, then it works. In all 3 cases the action= value is a relative URL. The failing case is different because the iframe src is generated by javascript. It actually shows 2 iframe cases that work, and one that doesn't. Details Ok, I got a test case from, and cleaned it up a bit. Test case, shows iframe cases that work & don't work
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |