5 Replies Latest reply on Jun 6, 2012 8:33 PM by kcbabo

    Config Update for SOAP Gateway

    kcbabo

      Can we update the SOAP gateway config to have the following options (in order):

       

      WSDL URI (required) : string

      WSDL Port : string

      Context Path : string

      Server Port : int

      Unwrapped Payload : boolean (default to false)

      Context Mapping : enum {CONFIG, DOM, VALUE, XML}

       

      Schema is here:

      https://github.com/jboss-switchyard/components/blob/master/soap/src/main/resources/org/switchyard/component/soap/config/model/v1/soap-v1.xsd

       

      An example with all of the above options:

      <soap:binding.soap>
              <soap:contextMapper soapHeadersType="VALUE"/>
              <soap:messageComposer unwrapped="true"/>
              <soap:wsdl>target/test-classes/org/switchyard/component/soap/Payments.wsdl</soap:wsdl>
              <soap:wsdlPort>PaymentsPort</soap:wsdlPort>
              <soap:socketAddr>:18001</soap:socketAddr>
              <soap:contextPath>PaymentsService</soap:contextPath>
      </soap:binding.soap>
      

       

      Updated schema will be available once this is pushed:

      https://github.com/jboss-switchyard/components/pull/328

        • 1. Re: Config Update for SOAP Gateway
          bfitzpat

          Ok, have done the model changes and issued a pull request for SWITCHYARD-832

          • 2. Re: Config Update for SOAP Gateway
            kcbabo

            Hey - can we default contextPath to the application name?  That would be lovely.

            • 3. Re: Config Update for SOAP Gateway
              dward

              +100

              • 4. Re: Config Update for SOAP Gateway
                noelo

                Just an fyi..

                In the ESB project, a few of the http gateway components use the ESB file name as a non-changable part of context name.

                I've seen this cause issues with a few customers where they deploy maven built esb archives but the URLs change due to the changes in the archive versioning.

                They'd perfer that a minor change to a deployable doesn't result in a url change.

                 

                This might be something to keep in mind when building the context.

                 

                cheers

                Noel

                • 5. Re: Config Update for SOAP Gateway
                  kcbabo


                  Hey Noel,

                   

                  I don't think that will be a problem here as we are just talking about defaulting a contextPath setting in the binding configuration page.  The user is free to change it to whatever they want, i.e. they have full control.  Hopefully, that will provide enough flexibility, but if you see a danger there then please let us know.

                   

                  cheers,

                  keith