Uploaded image for project: 'SwitchYard'
  1. SwitchYard
  2. SWITCHYARD-1997

Dynamic "per message" endpoint

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    Description

      It would be nice to have an easy way to set the reference endpoint at runtime for every call.
      Use cases:

      • To allow to configure different endpoint per environment, so there is no need to recompile the application or use System.property to set endpoints.
      • To allow a service to invoke different endpoints depending on a "logic" in a component.
      • To provide with greater flexibility on service creation.

      For this, an option could be to provide hook points in the OutboundHandler so the endpoint for the ServiceReference that has been set-up through the configuration can be obtained from some other place.

      E.g:

       String toAddress = SOAPUtil.getToAddress(exchange.getContext());  
 if (address == null){ // This means there is no Addressing, so endpoint can be overwritten if configured  
    toAddress = InjectAddressFromCache(); // Probably with a hook point could be better, to be able to set toAddress depending on ServiceName or whatever  
 }  
 if (toAddress != null) {  
      _dispatcher.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, toAddress);  
 }

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users SWITCHYARD-2448 Support dynamic modification of parameters for gateway service/reference bindings

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is followed up by

          Feature Request - Feature requests from customers and/or users SWITCHYARD-2844 Add common property alias collection to handle binding specific context properties

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open
          is related to

          Enhancement - An enhancement or refactoring of existing functionality ENTESB-4585 SwitchYard: dynamic "per message" endpoint

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users SWITCHYARD-1916 Allow HTTP reference binding to accept HTTP method, request URI, query string, etc. dynamically

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              toigaras@redhat.com tomohisa igarashi
              jmorales@redhat.com Jorge Morales Pou (Inactive)
              Archiver:
              ranumula@redhat.com Raju Anumula

              Dates

                Created:
                Updated:
                Resolved:
                Archived: