[jira] Commented: (SM-1155) New component: OSWorkflow JBI Component

["Bruce Snyder (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40747 ] 

Bruce Snyder commented on SM-1155:
----------------------------------

To accept this contribution, it will need the following: 

* Javadocs 
* A page on the ServiceMix wiki describing the component 
* A working test 
* Code styled according to the ServiceMix Checkstyle rules 
* The contribution should be a unified diff 

The last two points are easier to achieve if the code is developed using the ServiceMix code base. This will automatically run the Checkstyle rules and tell you what's wrong and it will allow you to very easily create a unified diff. 

It would also be really helpful if you could create a Maven archetype for this component. These are really easy to create and they really help people to use the component. 

> New component: OSWorkflow JBI Component
> ---------------------------------------
>
>                 Key: SM-1155
>                 URL: https://issues.apache.org/activemq/browse/SM-1155
>             Project: ServiceMix
>          Issue Type: Improvement
>            Reporter: Lars Heinemann
>            Priority: Minor
>         Attachments: cp-osworkflow.tar
>
>
> New component: OSWorkflow JBI Component
> I attached a first very basic approach of an OSWorkflow service engine as example.
> Compart Systemhaus GmbH is granting all remaining rights to the ASF.
> To build a service unit:
> You need to have in your SU's resources:
> - osworkflow.xml
> - workflows.xml
> - xbean.xml
> - your custom workflow xml file referenced inside workflows.xml
> Then just write Conditions, Functions, etc. as java classes or use other OSWorkflow logic as you need.
> Important to note:
> The transient vars contain some important objects for your use...
> Key                                                                  -             Value
> OSWorkflow.KEY_IN_MESSAGE              -             the received normalized "in" message which started the workflow
> OSWorkflow.KEY_EXCHANGE                 -             the received message exchange which started the workflow
> OSWorkflow.KEY_ENDPOINT                   -            the instance of OSWorkflowEndpoint which processes the workflow
> The message received is not answered until you do it inside the workflow. Also the processing of the message exchange / in message content as well as sending an answer has to be done from inside your workflow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.