Currently not possible to adjust profile locations without modifying system files
Basics
Logistics
Basics
Logistics
Description
We really need a way to manage built-in flow locations that doesn't hardcode them in webflow-config.xml
I think I originally was under the impression that properties didn't work there, but they do (we're using one) so this is probably no harder than just defining some defaulted properties and letting people know what they are in the rare cases they need to change.
Environment
None
Attachments
1
spring-webflow.patch
26 Feb, 2016
Activity
Scott Cantor
July 19, 2016 at 8:30 PM
All the relevant work was done in IDP-966, and we're no longer dependent on the Spring patch either way.
It isn't actually possible to turn off the built-in paths, or at least I didn't bother with that, but it is possible to mount system flows at additional locations, which is the main requirement.
Scott Cantor
February 26, 2016 at 8:11 PM
Attached the patch I submitted to Spring, it works for our use cases. Given how simple this is if it's done "right", I'm inclined to just live with the limitation for now and let them fix it.
Scott Cantor
February 26, 2016 at 7:24 PM
Got SWF to build out of git with Gradle and was able to redirect our testbed to a snapshot for testing.
Tested a really simple patch to indirect FlowLocation objects through BeanDefinitionBuilders and successfully tested property replacement for the locations. Will work on a more thorough patch to submit to SWF.
Scott Cantor
February 26, 2016 at 4:56 PM
They asked for a patch, so worth starting with that for now and trying to get it included.
Scott Cantor
February 23, 2016 at 2:59 AM
It looks like the "supported" way to build our own registry would be org.springframework.webflow.config.FlowDefinitionRegistryBuilder (which we'd have to drive with our own configuration schema).
We really need a way to manage built-in flow locations that doesn't hardcode them in webflow-config.xml
I think I originally was under the impression that properties didn't work there, but they do (we're using one) so this is probably no harder than just defining some defaulted properties and letting people know what they are in the rare cases they need to change.