Thanks Don. That clears things up for me some. I'm going to take a little
closer look and see if it is possible to make the page lookup more flexible.
If JSF is expecting the page to look this way, then it makes sense that it
may have to be this way. I'll let you know if I find a way to make i
Yeah, the JSP location could be made more flexible. I originally
coded it that way to match how JSF would expect to find and handle the
JSP. I don't remember, off hand, if other parts of the JSF controller
expects the JSP to be located as such. If you patch the code and find
it works fine, plea
Sure...first, the JSF interceptors trigger if there is a JSF result.
The result code from the action, even if it is a JSF action, is
treated like a normal Struts 2 result code, and therefore, subject to
the Struts 2 navigation. When the page is rendered, the Action
instance is injected into the J
Ok, I did some debugging and I think I figured out what it is doing. It
looks like it is using the namespace from the package definition plus the
name from the action definition plus the file suffix (jsp). To come up with
"/jsf/employee/list.jsp".
I'm not sure that this is going to be flexible
4 matches
Mail list logo
