Skip to content

Comments

MODE-1467 Added ability to explicitly invoke sequencer within session#943

Closed
rhauch wants to merge 1 commit intoModeShape:masterfrom
rhauch:mode-1467
Closed

MODE-1467 Added ability to explicitly invoke sequencer within session#943
rhauch wants to merge 1 commit intoModeShape:masterfrom
rhauch:mode-1467

Conversation

@rhauch
Copy link
Contributor

@rhauch rhauch commented Sep 12, 2013

ModeShape now supports applications explicitly invoking sequencing from within the scope of a session. There are several differences with using sequencers in this style:

  • A specific sequencer must be named, and only that sequencer will be invoked.
  • The path expressions of that configured sequencer are not used in any way. All other configured properties are still used.
  • The sequencer's accepted MIME types are still respected. If the input content's MIME type is known and is not in the sequencer's set of supported MIME types, the sequencing operation will return immediately.
  • The caller must supply the property containing the value to be sequenced.
  • The caller must supply a new node into which the sequencer output will be placed.
  • The session used to sequence contains all sequencing output as transient state; the caller is expected to call 'session.save()' if the output is to be persisted.

ModeShape now supports applications explicitly invoking sequencing
from within the scope of a session. There are several differences with
using sequencers in this style:

- A specific sequencer must be named, and only that sequencer will be
invoked.
- The path expressions of that configured sequencer are not used in
any way. All other configured properties are still used.
- The sequencer's accepted MIME types are still respected. If the
input content's MIME type is known and is not in the sequencer's set
of supported MIME types, the sequencing operation will return immediately.
- The caller must supply the property containing the value to be
sequenced.
- The caller must supply a new node into which the sequencer output
will be placed.
- The session used to sequence contains all sequencing output as
transient state; the caller is expected to call 'session.save()' if
the output is to be persisted.
@hchiorean
Copy link
Member

looks good

@rhauch
Copy link
Contributor Author

rhauch commented Sep 13, 2013

Rebased and merged into the 'master' branch.

@rhauch rhauch closed this Sep 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants