Craig McClanahan wrote:
On 12/21/05, Laurie Harper <[EMAIL PROTECTED]> wrote:
The context relative thing is not the behaviour I'm seeing though. If I
have a navigation rule that points to /foo/bar.jsp with redirect set,
the browser is redirected to /faces/foo/bar.jsp.
That would imply you have FacesServlet mapped to "/faces/*", right? This is
indeed the URL that the submit would have to go to. If you map FacesServlet
to "*.faces" instead, the emitted URl would be "/foo/bar.faces" instead.
Right, which still wouldn't give me what I was shooting for -- having
the to-view-id URL served by a different servlet. The original idea was
to have /faces/* mapped to the Faces servlet but route requests through
a separate servlet, say /view/*, which would know how to map logical
URLs to physical views and forward [I didn't describe that scheme in
this thread, though :-)].
I'm sold on the general principle that this isn't such a great idea, but
I'm still not sure I can get what I want any other way. I can use a
custom navigation handler to change the way to-view-id is handled,
though. I just can't see how to use one to avoid the seperate controller
servlet altogether (see following post).
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
