I think we should move the sequence selection to the Implementation Tab. Its not just related to this feature but selecting the sequences is more of an API Implementation detail rather than a management detail. Its the sequences that decide the transformations, etc. Therefore IMO it better suits the "Implementation" section.
Thanks, NuwanD. On Wed, Sep 9, 2015 at 7:45 AM, Isuru Udana <[email protected]> wrote: > Hi Abimaran, > > IMO we should not move the custom sequences option to implementation tab. > What we can do is, when user select the Default Endpoint type, we can show > a new mandatory field to select the sequence (which contains the logic to > pick the 'To' header). In that way we should be able to prevent possible > user errors. > > > > On Wed, Sep 9, 2015 at 6:39 AM, Dushan Abeyruwan <[email protected]> wrote: > >> Hi >> AFAIK, In-Flow can have any sequence, and its not must to select >> sequence which has To header, client can define To header any embedded >> sequence i.e (which can have many possibilities) think from simple scenario >> to complex scenario where client define complex custom extension. >> >> What I would think adding to NuwanD concern, when creating API you >> should validate the selected sequence (iterate through mediators and see >> whether it has To header defined) >> >> However ,to make this more interesting, I have seen people using service >> chaining within In or Out Synapse extensions (using callout mediator) guess >> what, callout mediator can have To header as well, then you need understand >> which To header used by API it self :) >> >> Cheers, >> Dushan >> >> >> On Tue, Sep 8, 2015 at 3:06 AM, Abimaran Kugathasan <[email protected]> >> wrote: >> >>> Hi All, >>> >>> Do we need to move the exsting "Message Mediation Policies" [1] which >>> handles adding in/out/fault sequences into API to Implementation tab from >>> Manage tab? Or Can we add this Default Endpoint sequence selection only in >>> the Implementation tab? >>> >>> [1]: >>> >>> >>> >>> On Mon, Sep 7, 2015 at 9:59 PM, Nuwan Dias <[email protected]> wrote: >>> >>>> One thing to note is that is Destination Based Stats should also work >>>> properly with dynamic endpoints. Need to keep that in mind when testing. >>>> Endpoint security should also be tested for both Basic Auth and Digest >>>> Auth. >>>> >>>> And when a user selects the "Default Endpoint" type, we should mandate >>>> him to select a custom in-sequence and provide appropriate messages to >>>> inform him that he should set the "To" header properly. >>>> >>>> Thanks, >>>> NuwanD. >>>> >>>> On Mon, Sep 7, 2015 at 2:16 PM, Abimaran Kugathasan <[email protected]> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> APIM 1.10.0 needs to support Default Endpoint [1] types. To support >>>>> it, API Publisher needs a way to define Custom Mediation Sequences to >>>>> assemble endpoint dynamically and import it into APIs. >>>>> >>>>> Currently, we can define/add Custom Mediation Sequences through >>>>> Management Console and, those will appear in the API Publisher's Manage >>>>> section under 'Message Mediation Policies'. >>>>> >>>>> We planned to move this to API Publisher's Implementation page, where >>>>> API Publisher can import the custom sequence into API when selecting >>>>> Default Endpoint for API. And, these sequences should run before the send >>>>> mediator to generate the endpoint dynamically. >>>>> >>>>> Please provide your suggestion on this. >>>>> >>>>> >>>>> [1] : https://docs.wso2.com/display/ESB481/Default+Endpoint >>>>> >>>>> -- >>>>> Thanks >>>>> Abimaran Kugathasan >>>>> >>>>> Software Engineer | WSO2 Inc >>>>> Data & APIs Technologies Team >>>>> Mobile : +94 773922820 >>>>> >>>>> <http://stackoverflow.com/users/515034> >>>>> <http://lk.linkedin.com/in/abimaran> >>>>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >>>>> <https://twitter.com/abimaran> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Technical Lead - WSO2, Inc. http://wso2.com >>>> email : [email protected] >>>> Phone : +94 777 775 729 >>>> >>> >>> >>> >>> -- >>> Thanks >>> Abimaran Kugathasan >>> >>> Software Engineer | WSO2 Inc >>> Data & APIs Technologies Team >>> Mobile : +94 773922820 >>> >>> <http://stackoverflow.com/users/515034> >>> <http://lk.linkedin.com/in/abimaran> >>> <http://www.lkabimaran.blogspot.com/> <https://github.com/abimarank> >>> <https://twitter.com/abimaran> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Dushan Abeyruwan | Technical Lead >> Technical Support-Bloomington US >> PMC Member Apache Synpase >> WSO2 Inc. http://wso2.com/ >> Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* >> Mobile:(001)812-391-7441 >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Isuru Udana* > Associate Technical Lead > WSO2 Inc.; http://wso2.com > email: [email protected] cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
