We have discussed about the $subject briefly during the cloud connector
reviews. So, let me summarize the approach that we are going to have for
ESB cloud connector tooling. Let me take the twitter connector as an
example :

- This is the structure of the connector archive : twitter-connector.zip
├── artifacts.xml
├── lib
│   └── twitter4j-1.0.0.wso2v1.jar
├── META-INF
├── org
│   └── wso2
│       └── carbon
│           └── mediation
│               └── library
│                   └── connectors
│                       └── twitter
│                           ├── AbstractTwitterConnector.class
│                           ├── TwitterClientLoader.class
│                           ├── TwitterConnectConstants.class
│                           ├── TwitterGetUserTimeLine.class
│                           ├── TwitterLoginUserMediator.class
│                           ├── TwitterMediatorUtils.class
│                           ├── TwitterRetweetStatusMediator.class
│                           ├── TwitterSearch.class
│                           ├── TwitterSearchPlaces.class
│                           ├── TwitterShowStatusMediator.class
│                           └── TwitterUpdateStatusMediator.class
├── twitter
│   ├── artifact.xml
│   ├── get_user_timeline.xml
│   ├── login_user.xml
│   ├── retweet_status.xml
│   ├── search_places.xml
│   ├── search_string.xml
│   ├── show_status.xml
│   └── update_status.xml
└── twitter4j.properties


- So, by inspecting the connector, we can find out the name of the
connector and its operations

├── twitter
│   ├── artifact.xml
│   ├── get_user_timeline.xml
│   ├── login_user.xml
│   ├── retweet_status.xml
│   ├── search_places.xml
│   ├── search_string.xml
│   ├── show_status.xml
│   └── update_status.xml


- Now we know all the supported operations by looking at the templates (
get_user_timeline.xml.. etc) and each template will give what are the
parameters needed for that operation.

- So, everything can be dynamically generated just by looking at the
connector archive. From DevS point of view, we can have a pallet for each
connector, along with the supported operations.

- Users simply drag and drop what ever the required connector operations (
eg: update_status, retweet_status etc)


Thanks,

-- 
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
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to