You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Netflexity (JIRA)" <ji...@apache.org> on 2007/07/11 00:28:33 UTC
[jira] Created: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
InOut to InOnly pattern Endpoint for eip-su
-------------------------------------------
Key: SM-999
URL: https://issues.apache.org/activemq/browse/SM-999
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-eip
Reporter: Netflexity
Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
Posted by "Netflexity (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39644 ]
Netflexity commented on SM-999:
-------------------------------
Pipeline is InOnly to InOut.
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
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-999) InOut to InOnly pattern
Endpoint for eip-su
Posted by "Andrea Zoppello (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39646 ]
Andrea Zoppello edited comment on SM-999 at 7/11/07 8:04 AM:
-------------------------------------------------------------
We've done something similar to this in spagic integration platform with "Synchronous Comm Point"
I'ts basically a component that handle an InOut communication with a binding component and propagate a InOnly exchange.
Then it mantains the original exchange and when it receives an InOnly back it will give back response in the binding components.
An example could be something like:
WS (InOut) > Sync (InOnly) > XSLT (InOnly) > Groovy Script (InOnly) > Sync
was:
We've done something similar to this in spagic integration platform with "Synchronous Comm Point"
I'ts basically a component that handle an InOut communication with a binding component and propagate a InOnly exchange.
Then it mantains the original exchange and when it receives an InOnly back it will give back response in the binding components.
An example could be something like:
WS ---(InOut) --> Sync -(InOnly)-> XSLT -(InOnly)-> Groovy Script -(InOnly)-> Sync
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39648 ]
Guillaume Nodet commented on SM-999:
------------------------------------
Unless I missed something, the attached code does not really handle the response and just sends back the input.
Andrea, do you have something working that you could give ?
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
Posted by "Netflexity (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Netflexity updated SM-999:
--------------------------
Attachment: InOutToInEndpoint.java
Here is the endpoint.
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
Posted by "Andrea Zoppello (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39646 ]
Andrea Zoppello commented on SM-999:
------------------------------------
We've done something similar to this in spagic integration platform with "Synchronous Comm Point"
I'ts basically a component that handle an InOut communication with a binding component and propagate a InOnly exchange.
Then it mantains the original exchange and when it receives an InOnly back it will give back response in the binding components.
An example could be something like:
WS ---(InOut) --> Sync -(InOnly)-> XSLT -(InOnly)-> Groovy Script -(InOnly)-> Sync
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
Posted by "Andrea Zoppello (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39650 ]
Andrea Zoppello commented on SM-999:
------------------------------------
Hi Guillaume,
Take a look at the code of the class "it.eng.spagosoa.smx.components.sync.Synchronizer" in the spagic-components distribution.
We need this component basically to address the use case where
1) "client applications" need to call a webservice binding component and to get a response
2) the process behind binding component could be quite complex ( not just only one se )
3) the process need to be modelled in visual tool ( Spagic Studio )
By the way if you look at the code you can see that basically the syncronizer that basically it manage an InOutExchange this is keep in and an InOnly exchange is created.
If you want more details the Spagic Components Guide contains an example of that.
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
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-999) InOut to InOnly pattern
Endpoint for eip-su
Posted by "Andrea Zoppello (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39650 ]
Andrea Zoppello edited comment on SM-999 at 7/12/07 12:19 AM:
--------------------------------------------------------------
Hi Guillaume,
Take a look at the code of the class "it.eng.spagosoa.smx.components.sync.Synchronizer" in the spagic-components distribution.
We need this component basically to address the use case where
1) "client applications" need to call a webservice binding component and to get a response
2) the process behind binding component could be quite complex ( not just only one se )
3) the process need to be modelled in visual tool ( Spagic Studio )
By the way if you look at the code you can see that basically it manage an InOutExchange this is keep in and an InOnly exchange is created.
If you want more details the Spagic Components Guide contains an example of that.
was:
Hi Guillaume,
Take a look at the code of the class "it.eng.spagosoa.smx.components.sync.Synchronizer" in the spagic-components distribution.
We need this component basically to address the use case where
1) "client applications" need to call a webservice binding component and to get a response
2) the process behind binding component could be quite complex ( not just only one se )
3) the process need to be modelled in visual tool ( Spagic Studio )
By the way if you look at the code you can see that basically the syncronizer that basically it manage an InOutExchange this is keep in and an InOnly exchange is created.
If you want more details the Spagic Components Guide contains an example of that.
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
> Attachments: InOutToInEndpoint.java
>
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-999) InOut to InOnly pattern Endpoint for
eip-su
Posted by "Piotr Bzdyl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39638 ]
Piotr Bzdyl commented on SM-999:
--------------------------------
There is already such a pattern - PipeLine - http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-Pipeline.
Or maybe you are referring to something else?
> InOut to InOnly pattern Endpoint for eip-su
> -------------------------------------------
>
> Key: SM-999
> URL: https://issues.apache.org/activemq/browse/SM-999
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-eip
> Reporter: Netflexity
>
> Please add the following pattern to be able to use components that support only InOnly MEPs for InOut components. Attached file illustrates the idea.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.