idpv3 and web flow : flow-location or flow-location-pattern ?

[Tom Zeller]

>> I also found the webflow:flow-registry/@base-path to be useful, so
>> that the flow references can be relative to that. I had not yet played
>> around with externalized type of config there for putting this stuff
>> outside the war, but it would be awesome if it were as simple as
>> putting a file:// URL in base-path.
>
>
> I played around with this for a few minutes.  The base-path can take a
> file:// URL there and that aspect seems to work fine as far as finding
> flows.  That includes bean-imports specified simply to reside in the
> same directory as the flow definition.

Great.

> I do see an issue with view-states with that config.  If you let it do
> its default thing of  resolving the view name based on the state id
> (i.e. no view-state/@view attribute present), it doesn't work by default
> to resolve it relative to the externalized flow-definition.
> Unfortunately it also doesn't work if you specify the view as an
> absolute file:// URL (that probably isn't even legal syntax, just tried
> for the hell of it).  It does work if you reference the view as a
> classpath resource.

Okay. I believe the planned view-state renderer is Velocity, which has
its own configurations for resource location, which might help.