Hi, a question to the list...
I am currently writing a chainable view handler
(a view handler which you can pass a sequential list of handlers
which are then chained together in the order you give in the parameters
- top down, all done in the faces config)
Now I rechecked the tlds and I saw that you already can cascade the
decorating view handlers.
But one question to the people in here more familiar with the specs,
does this cascade enforce a calling order or not?
Within a given faces-config.xml file you should be able to count on ordering (the last one you declare will be "the" view handler from the point of view of the Application object. However, there's no mandated ordering with respect to view handlers loaded from different faces-config.xml files (for example, those implicitly loaded from the META-INF directory of a component JAR).
You may recall some earlier discussion on this list about what the JSF RI currently does -- essentially loading the jar files in alphabetical order. It's a convention, not a mandated requirement, and doesn't address all possible dependency relationships you might want, but it would be better than nothing.
Craig
I am not talking about the actual implementation here
but more about the specs themselves.
the * in the view handler tag definition makes that unclear.
If it does I can dump the work spent so far on the custom handler
if not, then it probably is a good idea to implement it fully.
