Hi, Developer Studio 3.3.0 provides the tooling support for connectors. But Developer Studio 3.3.0 documentation doesn't provides steps for that. We should update the document with necessary steps before the Developer Studio 3.3.0 release.
Viraj's blog [1] will helpful in creating document for connector tooling. [1] http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html Thanks and Regards, AsankaS. On Tue, Dec 3, 2013 at 12:47 PM, Samisa Abeysinghe <sam...@wso2.com> wrote: > I cannot seem to find any docs on how to use connectors form DevS. I think > that is a big missing piece. > > I thought DevS 3.3. was the way to develop with connectors for ESB 4.8. Or > should I use configs (that breaks the developer story I guess) > > > Thanks, > Samisa... > > > Samisa Abeysinghe > > Vice President Training > > WSO2 Inc. > http://wso2.com > > > > On Tue, Nov 19, 2013 at 1:50 AM, Jackie Wheeler <jac...@wso2.com> wrote: > >> Please summarize the changes so I can update the docs. I'm not sure we >> came to a final conclusion on naming. >> >> Thanks, >> Jackie >> >> >> On Mon, Nov 18, 2013 at 12:02 AM, Kasun Indrasiri <ka...@wso2.com> wrote: >> >>> Hi Shafreen, >>> >>> Lets get these changes in to the next build. >>> >>> >>> On Mon, Nov 11, 2013 at 7:47 AM, Isabelle Mauny <isabe...@wso2.com>wrote: >>> >>>> +1 - >>>> Please share a conclusion for this thread. >>>> >>>> Isabelle. >>>> >>>> ------ >>>> Isabelle Mauny >>>> Director, Product Management; WSO2, Inc.; http://wso2.com/ >>>> email: isabe...@wso2.com <isabe...@wso2.com> - mobile: +34 616050684 >>>> >>>> >>>> On Thu, Nov 7, 2013 at 7:57 PM, Jackie Wheeler <jac...@wso2.com> wrote: >>>> >>>>> Can we rename the configKey attribute to initKey to make it clearer? >>>>> >>>>> >>>>> On Thu, Nov 7, 2013 at 7:14 AM, Kasun Indrasiri <ka...@wso2.com>wrote: >>>>> >>>>>> 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 <dus...@wso2.com>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 <isabe...@wso2.com>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: isabe...@wso2.com <isabe...@wso2.com> - mobile: +34 >>>>>>>> 616050684 *- In USA (from Oct 27 till Nov 5th) * >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Nov 6, 2013 at 7:44 AM, Kasun Indrasiri <ka...@wso2.com>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/ >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Jackie Wheeler* >>>>> VP, Technical Content >>>>> WSO2, Inc. >>>>> Mobile: +1 510 725-2876 >>>>> http://wso2.com/ >>>>> >>>> >>>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> >> -- >> *Jackie Wheeler* >> VP, Technical Content >> WSO2, Inc. >> Mobile: +1 510 725-2876 >> http://wso2.com/ >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Asanka Sanjeewa* Senior Software Engineer Mobile: +94772532924 WSO2 Inc. http://wso2.com/ Blog: http://asanka-tech-blog.blogspot.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
