JSF ViewFactory hard codes view id to resource mapping behavior which limits flexibilty of ViewHandler viewId->resource mapping logic [SWF-810]

[spring-operator]

Keith Donald opened SWF-810 and commented

All view id->resource mapping logic should happen inside the ViewHandler.
The logic in resolveViewName of JsfViewFactory should be moved into that layer.
the view id passed to the view handler should simply be:
(String) viewIdExpression.getValue(context);

Alternatively, JsfViewFactory should be configurable with its on view id->resource strategy, but this seems questionable since the ViewHandler has this responsibility.

---

Issue Links:

• Flow Definition Registry can´t access XML flow definitions inside unexpanded web application archives. [SWF-784] #1547 Flow Definition Registry can´t access XML flow definitions inside unexpanded web application archives.

• The view path cannot be resolved if the flow is located in the classpath. [SWF-1319] #509 The view path cannot be resolved if the flow is located in the classpath.

1 votes, 2 watchers

[spring-operator]

Jeremy Grelle commented

Moved view resource resolution logic into FlowViewHandler