Craig McClanahan wrote:
On 1/19/06, Laurie Harper <[EMAIL PROTECTED]> wrote:
I have a custom ViewControllerMapper which depends on resources set up
by my ViewHandler implementation. Unfortunately, in some circumstances,
ShaleViewHandler calls the mapper before my view handler has done its
work. I think the problem is that ShaleViewHandler gets installed as a
wrapper around my view handler, rather than the other way round.
Is there anyway to control that? I'm pretty sure JSF doesn't provide a
way to do so, but was hoping this might be something Shale could help
with...
You are correct that there's no current way to control the order of view
handler initialization. For the specific case of choosing a
ViewControllerMapper instance, however, use the context init parameter
ShaleApplicationFilter.VIEW_CONTROLLER_MAPPER (the literal value is "
org.apache.shale.view.VIEW_CONTROLLER_MAPPER") to specify the fully
qualified class name. Shale's view handler will then use your
implementation.
Yeah, the mapper registration is working fine, it's just that it needs
resources that are initialized by the view handler, so I need my view
handler to be the outer-most one.
I guess I'll have to work around it by accessing that data via a static
helper method on the view handler that'll lazy-init the required
resources if necessary.
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
