Hi Json, Usually input should be passed to the connector as parameters. This should be simple strings.
Inside the connector you should construct the payload required by the api. Also login related stuff should be handled in the init method. eg: storing the accesstokens. Best Regards, Malaka On Fri, May 2, 2014 at 3:30 PM, Jason Catlin <[email protected]> wrote: > Hey, > > Question: is there something standard that people do, when writing > connectors, for arguments that are big complex data types? Can we set > up templates to take complex structured inputs, or just make them > write their own json, or what? > > jc > > On Fri, Apr 25, 2014 at 2:54 AM, Jason Catlin <[email protected]> wrote: > > Hey guys, > > > > just fyi, Malaka and I are working on a funny OAuth problem right now. > > Shouldnt be too bad, but somehow credentials don't seem to be making > > it through to the web service call. > > > > jc > > > > On Mon, Apr 21, 2014 at 7:30 PM, Malaka Silva <[email protected]> wrote: > >> Yes Indeed. Selecting the sections that are mostly use will do for the > first > >> version. > >> > >> > >> On Mon, Apr 21, 2014 at 6:00 PM, Shevan Goonetilleke <[email protected]> > >> wrote: > >>> > >>> Jason, we don't need to support all available functions. Let's define a > >>> set of use cases that we think are a must have for a first version and > >>> implement them. We can always do a V2 later based on user > response/feedback. > >>> > >>> > >>> On Mon, Apr 21, 2014 at 5:54 PM, Jason Catlin <[email protected]> wrote: > >>>> > >>>> Hey guys, > >>>> > >>>> So I was a bit mistaken before when I said this was a small API, cause > >>>> I was looking at the Youtube ANALYTICS api, which only has one > >>>> function that returns a report about usage. The actual mainline > >>>> Youtube api is HUGE, with all these functions for manipulating > >>>> playlists and subscriptions and channels and everything else. So > >>>> Malaka is right that this could take long, especially if I'm going to > >>>> take an actual Youtube account and test every one of these functions. > >>>> Now that's fine, I don't mind doing a big api, but this could take a > >>>> while. > >>>> > >>>> I'm just about done coding the very first version of the connector, > >>>> which just has the minimum functionality for each part. I'll keep > >>>> you guys posted about what happens next. > >>>> > >>>> jc > >>>> > >>>> On Fri, Apr 18, 2014 at 10:05 PM, Nuwan Bandara <[email protected]> > wrote: > >>>> > Hi Jason, > >>>> > > >>>> > Hows the connector dev work progressing ? > >>>> > > >>>> > Regards, > >>>> > /Nuwan > >>>> > > >>>> > > >>>> > On Thu, Apr 10, 2014 at 4:33 AM, Jason Catlin <[email protected]> > wrote: > >>>> >> > >>>> >> Hey guys, > >>>> >> > >>>> >> As you know, the ESB has the ability to use connector plugins so > that > >>>> >> you can easily make calls to common services without having to > >>>> >> re-implement the details. We want a rich library of these, and > I'll > >>>> >> be contributing a few. I'll be starting with a youtube connector, > >>>> >> something relativley simple, and then doing more complicated ones > >>>> >> later. > >>>> >> > >>>> >> So I looked through all the connectors already implemented and > >>>> >> determined that the twitter connector is probably the most similar > to > >>>> >> what I'll be doing. The authentication is very similar, and then > both > >>>> >> just have a few simple queries made through REST interfaces. > >>>> >> > >>>> >> A few points of interest: Even though the ESB Connector system > has a > >>>> >> way to specify REST connectors, the twitter connector doesn't use > >>>> >> this, and rather uses a Java coded one instead. Does anyone know > what > >>>> >> the reason for this is? > >>>> >> > >>>> >> Also, I noticed that the twitter connector forms an OAuth token > inside > >>>> >> the Java code, and it gets its authentication details from > properties > >>>> >> that it reads form the configuration of the connector. This is one > >>>> >> way to do it. Another way, which might make more sense to me, is > for > >>>> >> the connector to ignore the OAuth all together, and have the user > add > >>>> >> that header outside the connector. This might give them much more > >>>> >> control over it. Does anyone know why they set up the twitter > >>>> >> connector that way? > >>>> >> > >>>> >> In general, I think this will probably be a pretty open and shut > >>>> >> project. I'd be suprised if it takes more than a week. > >>>> >> > >>>> >> JC > >>>> > > >>>> > > >>>> > > >>>> > > >>>> > -- > >>>> > Thanks & Regards, > >>>> > > >>>> > Nuwan Bandara | Senior Technical Lead - Solutions Architecture, > WSO2 > >>>> > Inc. > >>>> > +1 812.606.7390 | +1 650.745.4499 Ext 4210 | http://nuwanbando.com > >>>> _______________________________________________ > >>>> Architecture mailing list > >>>> [email protected] > >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >>> > >>> > >>> > >>> > >>> -- > >>> Shevan Goonetilleke > >>> Director of Engineering > >>> WSO2, Inc. > >>> lean.enterprise.middleware > >>> m: +94777340680 > >>> w: http://wso2.com > >>> > >>> _______________________________________________ > >>> Architecture mailing list > >>> [email protected] > >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >>> > >> > >> > >> > >> -- > >> > >> Best Regards, > >> > >> Malaka Silva > >> Senior Tech Lead > >> M: +94 777 219 791 > >> Tel : 94 11 214 5345 > >> Fax :94 11 2145300 > >> Skype : malaka.sampath.silva > >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > >> Blog : http://mrmalakasilva.blogspot.com/ > >> > >> WSO2, Inc. > >> lean . enterprise . middleware > >> http://www.wso2.com/ > >> http://www.wso2.com/about/team/malaka-silva/ > >> > >> Save a tree -Conserve nature & Save the world for your future. Print > this > >> email only if it is absolutely necessary. > >> > >> _______________________________________________ > >> Architecture mailing list > >> [email protected] > >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >> > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/<http://wso2.com/about/team/malaka-silva/> Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
