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

[Tom Zeller]

> As I mentioned in the note I just sent, it certainly works fine to use a
> flow-location along with a file:// URL base-path.
>
> Actually, what *didn't* work was a pattern like this with a file:// URL
> base-path:
>
> <webflow:flow-location-pattern value="/**/*-flow.xml"/>
>
> I didn't spend any time figuring out why, maybe with some tweaks that
> would work as well.

For the archives, given a flow-registry with base-path of
"file:<path>" and a flow-location-pattern, e.g.

<webflow:flow-registry base-path="file:/opt/idp/flows/" ...
  <webflow:flow-location-pattern value="/**/*-flow.xml" />

The flowId for a flow definition in /opt/idp/flows/test/test-flow.xml
will be "opt/idp/flows/test", which is not what we want.

This seems to be because the FlowDefinitionResourceFactory strips the
"classpath:" and "classpath*:" prefixes from the base-path, but not
"file:". Easy enough to fix, but I don't know how to plug in the fix
to Spring without overriding the FlowRegistryFactoryBean.

So, flow-location-pattern does not resolve flow ids properly given a
flow-registry base-path of "file:<path>".