User Configurable Flow at /idp/

Marvin Addison marvin.addison at gmail.com
Thu Sep 4 09:15:51 EDT 2014


> Another option:
>
> Stop mapping / for flows, and create mappings for only /profile/* and
> /status initially, and if people want to create other flows, they can
> modify web.xml and redeploy.

I really like the ability to add new functionality by dropping files
in the right location to install new flows. Lots of possibilities open
up if editing web.xml is an option, but lots of potential for mistakes
and maybe upgrade hassles. Why not put _all_ flows under /profile
(status would be a special case), which would allow the same
capability to define flows by copying files without needing to touch
web.xml?

Regarding your suggestion to put a forward in index.jsp, that's
definitely an option if the servlet mappings change. It's probably a
better option, in fact, than the one I proposed since it's more
generally flexible.

Should we create a Jira issue to track this feature?

M


More information about the dev mailing list