[jira] Issue Comment Edited: (SM-999) InOut to InOnly pattern Endpoint for eip-su

[Andrea Zoppello (JIRA)]

[ 
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] Issue Comment Edited: (SM-999) InOut to InOnly pattern Endpoint for eip-su

[Andrea Zoppello (JIRA)]

[ 
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.