Jun 29th, 2009, 11:20 AM
With the current base-path attribute on flowregistry the flowid becomes the directory path containing the flow. This is promotes the best-practice of a single flow per directory, however if the pattern is rather that an application has a single directory for flows and then would have subdirectories for various parts of the application and then want to keep related flows in the same directory there is no mechanism for namespacing.
For example if we have flows\hotel\booking.xml and flows\airline\booking.xml we are ok, because we will have flow ids hotel and airline.
But if we want flows\hotel\reservation.xml in addition to flows\hotel\booking.xml and flows\airline\reservation.xml and flows\airline\booking.xml there is currently no way to do this as far as I can tell. Is there any suggestion for a way to support this pattern.
Tags for this Thread