Q. Attribute used to handle web flow requests.

View solution

Q. JSF view handler to enable Facelets and a SpringBeanFacesELResolver to access Spring beans.

View solution

Q. To resolve Facelets views we configure:-

View solution

Q. File extension of a view state’s name which is by default loaded by facelet page.

View solution

Q. Navigation in traditional JSF applications is handled by:-

View solution

Q. For cross field validation or some sort of barrier to ensure state before you start a flow, we use.

View solution

Q. To use Spring Faces Components, we register which of the following?

View solution

Q. Resources retrieved by Spring Faces Component.

View solution

Q. Component which additionally provides a pop-up date picker control for its enclosed input field.

View solution

Q. Component which encloses command button.

View solution

Q. Libraries provided by RichFaces an integration support for Spring web flow.

View solution

Q. Design pattern implemented by Dispatcher Servlet.

View solution

Q. Class used to give a class behavior of a Dispatcher Servlet.

View solution

Q. Annotation for Controller Class.

View solution

Q. Handler method annotation.

View solution

Q. Method arguments that can be used in handler methods using the @RequestMapping annotation.

View solution

Q. Annotation which represents cookie values of requests.

View solution

Q. To add attributes to the model.

View solution

Q. To access the binding and validation result for the command object.

View solution

Q. To notify its completion of session processing.

View solution