You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Lars Heinemann (JIRA)" <ji...@apache.org> on 2007/11/29 12:39:26 UTC
[jira] Created: (SM-1155) New component: OSWorkflow JBI 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: osworkflow-example.tar
a workflow example
> 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: osworkflow-example.tar, 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: (was: servicemix-osworkflow.tar)
> 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
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Comment: was deleted
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Commented: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41411#action_41411 ]
Guillaume Nodet commented on SM-1155:
-------------------------------------
Will you be able to commit it to the trunk too ?
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: (was: cp-osworkflow.tar)
> 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
>
> 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.
[jira] Reopened: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann reopened SM-1155:
--------------------------------
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Fix For: 3.2.2, 3.3
>
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Comment: was deleted
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: servicemix-osworkflow.tar
forgot the clean it up....now the size is better :)
> 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.
[jira] Commented: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41409#action_41409 ]
Lars Heinemann commented on SM-1155:
------------------------------------
put to 3.2 branch
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Closed: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann closed SM-1155.
------------------------------
Fix Version/s: 3.2.2
3.3
Resolution: Fixed
Component is implemented. Additional sample will be added soon.
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Fix For: 3.2.2, 3.3
>
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "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 11/30/07 6:53 AM:
--------------------------------------------------------------
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)
- the wiki for this SE
- anything else?
was (Author: lhe):
Updated version of the OSWorkflow SE
- with smx code style
- using smx packenames
- with archetype
- with diff file
> 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.
[jira] Assigned: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann reassigned SM-1155:
----------------------------------
Assignee: Lars Heinemann
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41409#action_41409 ]
lhe edited comment on SM-1155 at 2/26/08 11:52 AM:
--------------------------------------------------------------
put to 3.2 branch
put to 3.3 trunk
was (Author: lhe):
put to 3.2 branch
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "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 ]
bsnyder edited comment on SM-1155 at 11/29/07 8:05 PM:
------------------------------------------------------------
To accept this contribution, it will need the following to be added/improved:
* 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 when you run the Maven build and it will allow you to very easily create a unified diff (see [svn diff|http://svnbook.red-bean.com/en/1.0/re09.html]).
It would also be really helpful if you could [create a Maven archetype|http://maven.apache.org/guides/mini/guide-creating-archetypes.html] for this component. These are easy to create and they really help people to use the component.
was (Author: bsnyder):
To accept this contribution, it will need the following to be added/improved:
* 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "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 11/30/07 7:04 AM:
--------------------------------------------------------------
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?
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)
- 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1155:
--------------------------------
Component/s: servicemix-osworkflow
> New component: OSWorkflow JBI Component
> ---------------------------------------
>
> Key: SM-1155
> URL: https://issues.apache.org/activemq/browse/SM-1155
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-osworkflow
> Reporter: Lars Heinemann
> Assignee: Lars Heinemann
> Priority: Minor
> Fix For: 3.2.2, 3.3
>
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-1155:
--------------------------------
Fix Version/s: servicemix-osworkflow-2008.01
> New component: OSWorkflow JBI Component
> ---------------------------------------
>
> Key: SM-1155
> URL: https://issues.apache.org/activemq/browse/SM-1155
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-osworkflow
> Reporter: Lars Heinemann
> Assignee: Lars Heinemann
> Priority: Minor
> Fix For: 3.2.2, 3.3, servicemix-osworkflow-2008.01
>
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Comment: was deleted
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Commented: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40757 ]
Lars Heinemann commented on SM-1155:
------------------------------------
Bruce,
actually I am working on it.
I will update this issue when I am finished.
Lars
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Comment: was deleted
> 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: osworkflow-example.tar, 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.
[jira] Work started: (SM-1155) New component: OSWorkflow JBI
Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SM-1155 started by Lars Heinemann.
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "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.
[jira] Resolved: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann resolved SM-1155.
--------------------------------
Resolution: Fixed
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Fix For: 3.2.2, 3.3
>
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "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 ]
bsnyder edited comment on SM-1155 at 11/29/07 8:02 PM:
------------------------------------------------------------
To accept this contribution, it will need the following to be added/improved:
* 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.
was (Author: bsnyder):
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.
[jira] Commented: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40919 ]
Bruce Snyder commented on SM-1155:
----------------------------------
The diff in the attached tarball does not contain any of the new files. In order to include the newly created files in the diff, you need to do a [{{svn add}}|http://svnbook.red-bean.com/en/1.0/re01.html] in your local copy to schedule the addition of the new files. Then run {{svn diff}} to create the diff file. This will include the new files in the diff file.
> 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: osworkflow-example.tar, 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.
[jira] Commented: (SM-1155) New component: OSWorkflow JBI Component
Posted by "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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40761 ]
lhe edited comment on SM-1155 at 11/30/07 6:59 AM:
--------------------------------------------------------------
forgot to clean it up....now the size is better :)
was (Author: lhe):
forgot the clean it up....now the size is better :)
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: cp-osworkflow.tar
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: servicemix-osworkflow.tar
Updated version of the OSWorkflow SE
- with smx code style
- using smx packenames
- with archetype
- with diff file
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41409#action_41409 ]
lhe edited comment on SM-1155 at 2/26/08 11:52 AM:
--------------------------------------------------------------
put to 3.2 branch
put to trunk
was (Author: lhe):
put to 3.2 branch
put to 3.3 trunk
> 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
> Assignee: Lars Heinemann
> Priority: Minor
> Attachments: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: osworkflow.diff
Bruce,
I now attached a complete diff file.
Regards,
Lars
> 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: osworkflow-example.tar, osworkflow.diff
>
>
> 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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Attachment: (was: servicemix-osworkflow.tar)
> 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: osworkflow-example.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.
[jira] Updated: (SM-1155) New component: OSWorkflow JBI Component
Posted by "Lars Heinemann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Heinemann updated SM-1155:
-------------------------------
Comment: was deleted
> 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.
[jira] Issue Comment Edited: (SM-1155) New component: OSWorkflow
JBI Component
Posted by "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/11/07 2:11 AM:
--------------------------------------------------------------
Updated version of the OSWorkflow SE
- with smx code style
- using smx package names
- with archetype
- with diff file
- added an example
The wiki for this service engine is finished and online.
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. Another example is provided within the samples folder.
@Bruce:
Please be so kind and add the new archetype to the smx.bat / smx.sh.
I was not able to get the example deployed correctly to the example folder. Could
you please manage this?
I think all requirements are now fullfilled or am I wrong? If something is still missing, just
let me know.
was (Author: lhe):
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.
> 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: osworkflow-example.tar, 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.