[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow JBI Component

["Lars Heinemann (JIRA)" <ji...@apache.org>]

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

lhe edited comment on SM-1155 at 12/3/07 12:39 AM:
--------------------------------------------------------------

Updated version of the OSWorkflow SE

- with smx code style
- using smx package names
- with archetype
- with diff file

The wiki for this service engine is finished but not yet replicated to the website.
When creating a service unit using the archetype, you will receive a full sample
workflow with a sample function and a sample condition. This is a good starting 
point for working with this SE.

@Bruce:
Please be so kind and add the new archetype to the smx.bat / smx.sh.


      was (Author: lhe):
    Updated version of the OSWorkflow SE

- with smx code style
- using smx package names
- with archetype
- with diff file

Still missing:
- the example (btw. the component test of the se is a working example and also when using the archetype you get a running example with 1 examplecondition and 1 examplefunction)
- the wiki for this SE
- anything else?

  
> 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: servicemix-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.