Hi
- 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.
>
+1 IMO this has to be a pre-configurable location, where customer is
freely asks to point where the connectors are gonna stored in dev location
so, once dev points to the connector archive folder, DevS should populate
all the available connectors to the pallet..
>
> - Users simply drag and drop what ever the required connector operations (
> eg: update_status, retweet_status etc)
>
this should be more closer to the call-template (what I felt only
dynamic behavior getting involved), and I think we can populate child
artifact.xml and populate all it's operations.
Once the operation selected, it's gonna be same as selecting
template, then populating the parameters... ideally this brings the generic
thus all other connectors can follow up the same setup.
Additionally each connector wrapped up with it's own icon, where
during the pallet initialization time those icons can be loaded
dynamically..
>
> Thanks,
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 71 536 4128
> Blog : http://kasunpanorama.blogspot.com/
>
--
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
