Let me try to write the config for this :
//As the first step, we may initiate the connector with 'init' for user
'foo'
*<twitter.init>*
* <consumerSecret>xx</consumerSecret>*
*
<accessTokenSecret>{wso2:vault-lookup('foo_ats')}</accessTokenSecret>*
* <accessToken>{wso2:vault-lookup('foo_at')}</accessToken>*
* <consumerKey>{wso2:vault-lookup('foo_ck')}</consumerKey>*
* </twitter.init>*
//Now I'm using the initiated connector (with user 'foo')
*<twitter.sendDirectMessage>*
* <userID>xxx</userID>*
* <message>xxx</message>*
*</twitter.sendDirectMessage>*
//Again using the same connector with user 'foo'
*<twitter.search>*
* <search>wso2</search>*
*</twitter.search>*
// Now I need to invoke an operation with a different twitter configuration
for user 'bar'.
*<twitter.sendDirectMessage configKey="barTwitterConfig">*
* <userID>xxx</userID>*
* <message>xxx</message>*
*</twitter.sendDirectMessage>*
//Now should I override the current config with 'barTwitterConfig' or use
the initiated 'foo' config?
*<twitter.search>*
* <search>wso2</search>*
*</twitter.search>*
The connector config can be externalize as follows.
Local Entry :
*<localEntry xmlns="http://ws.apache.org/ns/synapse
<http://ws.apache.org/ns/synapse>" key="kasunTwitterConfig">*
* <twitter.config>*
* <consumerSecret>xx</consumerSecret>*
* <accessTokenSecret>{wso2:vault-lookup('xx')}</accessTokenSecret>*
* <accessToken>{wso2:vault-lookup('aa')}</accessToken>*
* <consumerKey>{wso2:vault-lookup('bb')}</consumerKey>*
* </twitter.config>*
*</localEntry>*
This may be not the ideal config, but we need to build something around
this.
On Thu, Nov 7, 2013 at 5:43 AM, Dushan Abeyruwan <[email protected]> wrote:
> Hi Kasun,
> Now if this call init instead config, this will conflict with configRef,
> feeling something mismatching..
>
> <twitter.sendDirectMessage configKey="xxxx">
>
> <userID>xxx</userID>
>
> <message>xxx</message>
>
> </twitter.sendDirectMessage>
>
>
>
> On Thu, Nov 7, 2013 at 3:55 PM, Isabelle Mauny <[email protected]> wrote:
>
>> +1 on changing to *init* instead of config. My only concern is that init
>> does not imply (in the name) that credentials are being used to connect
>> somewhere but I agree login might be too restrictive, so we need to
>> compromise.
>>
>> I would also put the second enhancement as part of next milestone. Then
>> do an internal review and decide on the last part then ( auto-completion ).
>>
>> Thanks,
>> Isabelle.
>>
>> ------
>> Isabelle Mauny
>> Director, Product Management; WSO2, Inc.; http://wso2.com/
>> email: [email protected] <[email protected]> - mobile: +34 616050684 *-
>> In USA (from Oct 27 till Nov 5th) *
>>
>>
>> On Wed, Nov 6, 2013 at 7:44 AM, Kasun Indrasiri <[email protected]> wrote:
>>
>>> We had several offline discussions on the $subject and we came up with
>>> some enhancements.
>>>
>>>
>>> *Renaming connector 'config' operation *
>>>
>>> It seems using 'config' as an operation in a given connector is bit
>>> confusing.
>>> These are the alternatives that we have discussed.
>>>
>>> *"twitter.login"* - (IMO, loging is not a generic term and that might
>>> depends on the API that we are using)
>>>
>>> *"twitter.init"* - We can init a connector and then invoke any
>>> operation. If we want to switch to a different config, we can again to an
>>> init with a different config and so on.
>>>
>>> (We need these changes for 4.8)
>>>
>>> *Registry Browser for selecting connector config (DevS)*
>>>
>>> Add a registry browser button in the Init Ref(or config) property field
>>> in Dev Studio so that users don't have to remember and type the Init
>>> configuration's registry path in the field but can select it.
>>>
>>> *Field Auto-completion (DevS/connectors) *
>>>
>>> We need to be able to provide auto-complete and documentation on each
>>> operation, so we talked about generating XSDs for them. The XSDs can be
>>> part of the connector archive. However, we will be able to add this in a
>>> future ESB release.
>>>
>>> Please share your thoughts and incorporate the required changes in to
>>> 4.8.
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/ <http://wso2.com/>*
> *Mobile:(+94)714408632 <%28%2B94%29714408632>*
>
--
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
