[Architecture] ESB Review with Paul and Sanjiva: {2013-08-28}
Hi
Please find the notes for the discussion we had during the ESB review
meeting,
*Connector Archive modification*
- Connector list rename Import enable.
- Connector operations description remove synapse library part in end.
- Import[enable] link change once import is done.
- Rename artifact.xml connector.xml.
in conncetor.xml change toot element to connector and component as sub
element
*connector*
*component* name=twilio package=org.wso2.carbon.connectors
dependency *component*=twilio-cloud-connector-conference
/
dependency component=twilio-cloud-connector-account /
dependency component=twilio-cloud-connector-application /
descriptionSynapse library for Twilio
connector/description
/component
/connector
- *Icon inside connector archive* - this can be shown near the connector
name in the UI.
*New Language Re-factoring Proposals*
- In seq only model
seq
prop
log
mapper.../
callendpoint...//call {new Non Blocking callout}
mapper2 (questions: 1) which direction is the message in now? FORWARD
2) what is the payload? RESPONSE
callendpoint...//call {new Non Blocking callout}
mapper
respond/
/seq
- Timer method
seq cron=0 0 0 4 0 0
prop
log
mapper.../
callendpoint...//call
mapper2 (questions: 1) which direction is the message in now? FORWARD
2) what is the payload? RESPONSE
callendpoint...//call
/seq
- In-out example
seq
prop
log
mapper.../
callendpoint...//call
mapper2 (questions: 1) which direction is the message in now? FORWARD
2) what is the payload? RESPONSE
callendpoint...//call
mapper
loopback/
/seq
out
...
respond/
/out
- Callout-nonblocking ( *Call* mediator a new mediator will be
implemented instead send continuation=true ),
- i,e call blocking =false - true default .
- *depreciate* *Callout* mediator when *call blocking=true.*
- Task API for synapse that can work with TasksServer
*Additional*
- MQTT ProtocolBuffer implementation and the analysis will be initiated
by Ishan.
Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632 *
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Review with Paul and Sanjiva: {2013-08-28}
Hi Had a spacing issue the mail which I sent bit earlier, please find the notes with the correct format. *Connector Archive modification* - Connector list rename Import enable. - Connector operations description remove synapse library part in end. - Import[enable] link change once import is done. - Rename artifact.xml connector.xml. in conncetor.xml change toot element to connector and component as sub element *connector* *component* name=twilio package=org.wso2.carbon.connectors dependency *component*=twilio-cloud-connector-conference / dependency component=twilio-cloud-connector-account / dependency component=twilio-cloud-connector-application / descriptionSynapse library for Twilio connector/description /component /connector - *Icon inside connector archive* - this can be shown near the connector name in the UI. *New Language Re-factoring Proposals* - In seq only model *seq* * prop* * log* * mapper.../* * callendpoint...//call* * mapper2 (questions: 1) which direction is the message in now? FORWARD 2) what is the payload? RESPONSE* * callendpoint...//call* * mapper* * respond/* */seq* - Timer method *seq cron=0 0 0 4 0 0* * prop* * log* * mapper.../* * callendpoint...//call* * mapper2 (questions: 1) which direction is the message in now? FORWARD 2) what is the payload? RESPONSE* * callendpoint...//call* */seq* - In-out example *seq* * prop* * log* * mapper.../* * callendpoint...//call* * mapper2 (questions: 1) which direction is the message in now? FORWARD 2) what is the payload? RESPONSE* * callendpoint...//call* * mapper* * loopback/* */seq* *out* *...* *respond/* */out* - Callout-nonblocking ( *Call* mediator a new mediator will be implemented instead send continuation=true ), - i,e call blocking =false - true default . - *depreciate* *Callout* mediator when *call blocking=true.* - Task API for synapse that can work with TasksServer *Additional* - MQTT ProtocolBuffer implementation and the analysis will be initiated by Ishan. Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Re: [Architecture] ESB Review with Paul and Sanjiva: {2013-08-28}
On Fri, Aug 30, 2013 at 10:31 AM, Dushan Abeyruwan dus...@wso2.com wrote: Hi Had a spacing issue the mail which I sent bit earlier, please find the notes with the correct format. *Connector Archive modification* - Connector list rename Import enable. - Connector operations description remove synapse library part in end. - Import[enable] link change once import is done. - Rename artifact.xml connector.xml. in conncetor.xml change toot element to connector and component as sub element *connector* *component* name=twilio package=org.wso2.carbon.connectors dependency *component*=twilio-cloud-connector-conference / dependency component=twilio-cloud-connector-account / dependency component=twilio-cloud-connector-application / descriptionSynapse library for Twilio connector/description /component /connector - *Icon inside connector archive* - this can be shown near the connector name in the UI. *New Language Re-factoring Proposals* - In seq only model *seq* * prop* * log* * mapper.../* * callendpoint...//call* * mapper2 (questions: 1) which direction is the message in now? FORWARD 2) what is the payload? RESPONSE* * callendpoint...//call* * mapper* * respond/* */seq* - Timer method *seq cron=0 0 0 4 0 0* * prop* * log* * mapper.../* * callendpoint...//call* * mapper2 (questions: 1) which direction is the message in now? FORWARD 2) what is the payload? RESPONSE* * callendpoint...//call* */seq* - In-out example *seq* * prop* * log* * mapper.../* * callendpoint...//call* * mapper2 (questions: 1) which direction is the message in now? FORWARD 2) what is the payload? RESPONSE* * callendpoint...//call* * mapper* * loopback/* */seq* *out* *...* *respond/* */out* - Callout-nonblocking ( *Call* mediator a new mediator will be implemented instead send continuation=true ), - i,e call blocking =false - true default . - *depreciate* *Callout* mediator when *call blocking=true.* - Task API for synapse that can work with TasksServer *Additional* - MQTT ProtocolBuffer implementation and the analysis will be initiated by Ishan. MQTT - With 4.8 we are planning have this as an experimental feature. Protocol Buffers - PoC implementation with script mediator Cheers, Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 536 4128 Blog : http://kasunpanorama.blogspot.com/ ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
