I've built and installed a distribution workflow module based on
matterhorn-distribution-service-streaming. I worked on this a while ago
and I believe I then ran into a problem that the workflow step wasn't
recognized. Once I added the OSGI definition to matterhorn-conductor
the problem went away. So I thought that all workflow steps needed to
be registered explicitly in matterhorn-conductor. Am I doing something
wrong?
Thanks,
Chris
On 3/12/12 9:10 PM, Christopher Brooks wrote:
Chris,
There is really no need to stick new workflow operations into the
conductor bundle, they may as well live in their own bundle, e.g
matterhorn-comductor-myinstitution.
I like this idea but I don't understand what you mean by their own
bundle. Would this be a replacement for matterhorn-conductor or live
alongside it? What would the new bundle include in it? Thanks for
helping me to understand this better.
Check out these instructions, they show how to build a new bundle and
insert it into an existing Jetty:
http://opencast.jira.com/svn/MH/contrib/workflow-operation-handlers/1.1.x/EmailWorkflowOperationHandler/README.TXT
If you are only building a workflow operation handler, consider using
this template project:
http://opencast.jira.com/svn/MH/contrib/workflow-operation-handlers/1.1.x/template/
Chris
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
