On Wed, Jul 24, 2013 at 4:14 PM, Samisa Abeysinghe <[email protected]> wrote:
> OK, so, it should be at proxy level. If there are two twitter connectors
> for a proxy, they will be defined as twitterYou and twitterMe within the
> proxy scope. And we can re-use them in sequences as we wish.
>
I don't think I understand what that means ... connector "instances" are
not named - so what does twitterYou an twitterMe mean when there's no
config separated? If there's no config reference, there's only one config
in scope .. whatever was defined earlier in the sequence. So there's only
one around.
If you want to do a status update as "you" vs "me" then you'd need to
reenter <twitter.config> with the right creds and then use it (see below).
Dushan why are the properties named synapse.runtime.oauth.accessToken??
>> There are two problems with this:
>> - this has NOTHING to do with Synapse so its wrong to synapse.runtime.*.
>> - second, MORE IMPORTANTLY, many mediators will have an oauth.accessToken
>> property! So this will not work .. it needs to be twitter.oauth.accessToken
>> (which is what I said the first time IIRC).
>>
>
I made a mistake here .. the property names should be possible to be
arbitrary - otherwise we can't do Samisa's scenario above of tweeting as X
and tweeting as Y:
<sequence>
<!-- tweet as sanjiva -->
<twitter.config>
<oauth.consumerSecret>{vault-lookup('*sanjiva*
.twitter.oauth.consumerSecret')}</oauth.consumerSecret>
<oauth.accessTokenSecret>{vault-lookup('sanjiva.twitter.outh.accessTokenSecret')}</oauth.accessTokenSecret>
<oauth.accessToken>{vault-lookup('sanjiva.twitter.oauth.accessToken')}</oauth.accessToken>
<oauth.consumerKey>{vault-lookup('sanjiva.twitter.oauth.consumerKey')}</oauth.consumerKey>
</twitter.config>
<twitter.updateStatus>Hello, World (from Sanjiva)</twitter.updateStatus>
<!-- tweet as samisa -->
<twitter.config>
<oauth.consumerSecret>{vault-lookup('*samisa*
.twitter.oauth.consumerSecret')}</oauth.consumerSecret>
<oauth.accessTokenSecret>{vault-lookup('saisa.twitter.outh.accessTokenSecret')}</oauth.accessTokenSecret>
<oauth.accessToken>{vault-lookup('samisa.twitter.oauth.accessToken')}</oauth.accessToken>
<oauth.consumerKey>{vault-lookup('samisa.twitter.oauth.consumerKey')}</oauth.consumerKey>
</twitter.config>
<twitter.updateStatus>Hello, World (from Samisa)</twitter.updateStatus>
</sequence>
Now someone just has to get the right info into the vault.
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/
email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/
Lean . Enterprise . Middleware
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
