It is currently possible to ship new webflows in an extension JAR (in /META-INF/net/shibboleth/idp/flows/). That's nice, but our custom "affiliation chooser" flow has one view and we would like to package it together with the flow definition in our JAR. Would it feasible to extend the resourceLoaderPath property of bean org.springframework.web.servlet.view.velocity.VelocityConfigurer (defined in system/conf/mvc-beans.xml) so it also searches in something like classpath*:/META-INF/net/shibboleth/idp/views/**?
It is currently possible to ship new webflows in an extension JAR (in
/META-INF/net/shibboleth/idp/flows/). That's nice, but our custom "affiliation chooser" flow has one view and we would like to package it together with the flow definition in our JAR. Would it feasible to extend theresourceLoaderPathproperty of beanorg.springframework.web.servlet.view.velocity.VelocityConfigurer(defined insystem/conf/mvc-beans.xml) so it also searches in something likeclasspath*:/META-INF/net/shibboleth/idp/views/**?(moved from SUPPORT-20)