Several ModeShape components when configured in WF require explicit user input for the name of the module where these components are located.

For example, to use ModeShape's built-in sequencers in WF, one has to declare them like:

<sequencer name="zip-sequencer" classname="zip" module="org.modeshape.sequencer.zip">
  <path-expression>/files(//*.zip[*])/jcr:content[@jcr:data] => /derived/zip/$1</path-expression>
</sequencer>

always requiring the module attribute.
Since these internal sequencers are entirely controlled by ModeShape, there's no reason why the module name can't be resolved automatically, based on the sequencer type.

This enhancement is about relaxing the module name requirement for built-in components.