Thanks all.

Yes, a text field in the Publisher GUI allowing a user to enter the URI-template would satisfy our requirement. Our use case is that we have client developers with access only to the Publisher application who need to be able to register APIs with uri-templates in them. Please let me know if you need more details.

Best,
Joe

On 10/07/2013 11:12 PM, Joseph Fonseka wrote:
Hi Joe

Will you be able to give us a use case in your context how URL-templates will be used. It will help us to come up with a UI to support it.

BTW this discussion thread is moved to our architecture list see http://wso2.com/mail/ .

Regards
Jo



On Thu, Oct 3, 2013 at 10:22 PM, Isabelle Mauny <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    Supporting HA endpoints is a customer requirements (HA and LB)

    I have another idea for this: if we package several templates for
    each endpoint , and allow users to just set the parameters for
    each template , we would cover 80% of cases. If somebody wants to
    register a new template they can create it in Studio and deploy it
    in the right registry location, as we do for sequences.

    @Joe,
    Would a text field, allowing you to enter the URI template be
    enough for your requirement ? As you found out, uri-template are
    supported by the underlying engine, but not at the UI level right
    now.

    Thanks,
    Isabelle.
    __________________________________________________

    *Isabelle Mauny
    *Director, Product Management; WSO2, Inc.; http://wso2.com/
    *
    *

    On Oct 3, 2013, at 11:23 AM, Kasun Indrasiri <[email protected]
    <mailto:[email protected]>> wrote:

    I don't think it is necessary to support all the endpoint
    supported from ESB. Following endpoint type would be sufficient
    in API-M context.

    - Address EP
    - HTTP EP - We dynamically formulate the EP address based on URI
    Templates.

    These EPs should be able to cater most of the requirements. Do we
    have to support LB/FO at API-GW level?



    On Thu, Oct 3, 2013 at 11:19 AM, Joseph Fonseka <[email protected]
    <mailto:[email protected]>> wrote:

        Hi Sanjiva

            Jo does this also address secured endpoints? E.g. basic
            auth secured or WSSec-UT or other (as long as its
            supported by the ESB)?


        The plan is to add most of the Endpoint configuration to the
        Publisher UI without over complicating it. So I guess we can
        handle WSSec-UT as well and basic auth is already supported
        by APIM.

                    From the above list do we need to ? and how to
                    include the following ?

                    1. Default Endpoint


            What does this mean?


        From what I read Default Endpoint is used to add QoS and
        other configurations to an endpoint which is resolved from
        the to address of message context.

                    2. HTTP Endpoint - This require to populate the
                    uri template during mediation.
                    3. Template Endpoint - You need to specify a
                    template when creating an endpoint.


            So this is a way to create an endpoint based on some info
            in the incoming request?


        Yes HTTP Endpoint has the ability to generate the BE Service
        Endpoint URI based on the message so you have to configure
        how to do it in the mediator. So this require to have UI in
        the publisher to configure the mediators. IMHO better to look
        at some use-cases before incorporating this.

                    Some of the above need additional configuration.
                    As I understood configure meditations and
                    defining templates. Do we have to provide UI for
                    them as well.


            I think we need to provide a UI to define these
            endpoints. Is there something other than that in your
            mind? By "templates" you didn't mean ESB templates right?


        Well in ESB you can create endpoint templates which can be
        one of the other endpoint types. When you want to create an
        endpoint using those templates you can use "Template Endpoint
        Type" in endpoint creation and select the relevant template.
        So do we need AM to support keeping predefined endpoint
        templates?

        Regards
        Jo

-- *Joseph Fonseka*
        Senior Tech Lead
        WSO2 Inc.; http://wso2.com <http://wso2.com/>
        lean.enterprise.middleware

        mobile: +94 772 512 430
        skype: jpfonseka



        _______________________________________________
        Architecture mailing list
        [email protected] <mailto:[email protected]>
        https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




-- Kasun Indrasiri
    Software Architect
    WSO2, Inc.; http://wso2.com <http://wso2.com/>
    lean.enterprise.middleware

    cell: +94 71 536 4128 <tel:%2B94%2071%20536%204128>
    Blog : http://kasunpanorama.blogspot.com/
    _______________________________________________
    Architecture mailing list
    [email protected] <mailto:[email protected]>
    https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


    _______________________________________________
    Architecture mailing list
    [email protected] <mailto:[email protected]>
    https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture




--

--
*Joseph Fonseka*
Senior Tech Lead
WSO2 Inc.; http://wso2.com <http://wso2.com/>
lean.enterprise.middleware

mobile: +94 772 512 430
skype: jpfonseka




_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to