We can't as synapse and apache are running in the same box. I feel its not a nice to have, but a required feature as most of the other mediation framework has this option.
Balaji pzfreo wrote: > > Balaji > > In the meantime, could you just set Synapse to listen on 8081 too? > > Paul > > On 8/7/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: >> Balaji >> >> Unfortunately we don't do this with 1.0. We can do a patch simply >> enough. I actually asked the Axis2 team to do this once before :-) So >> its nice to have a good reason. >> >> I'll raise a JIRA, and I'll see we can get you an update. We plan to >> have a 1.0.1 sometime soon, so if you can use a nightly build to test >> it shouldn't be long. >> >> Paul >> >> On 8/7/07, balaji hari <[EMAIL PROTECTED]> wrote: >> > >> > Hi, >> > >> > Thanks for getting back to us on this. But actually we have a web >> server >> > (proxy) sitting infront of synapse >> > which listens to https. >> > >> > This is how it looks like. >> > Forwards >> > (http) >> > Apache(https):8081 --------->Synapse(http):6666 >> > >> > So the client has to do >> > >> > https://freemantle.org:8081/soap/TestService >> > >> > but the synapse changes the soap:address in the generated wsdl to >> > >> > http://freemantle.org:6666/soap/TestService which we don't want. >> > >> > Appreciate if you could help us how to configure synapse to accomplish >> this? >> > >> > thanks >> > Balaji >> > >> > >> > >> > balaji hari wrote: >> > > >> > > Hi, >> > > >> > > We are using synapse as xml mediaiton framework. We configured a >> proxy >> > > service and specified WSDL URI. But synapse changed the URI in the >> > > generated WSDL based on machine name. >> > > >> > > <wsdl:service name="WpsServiceUT"> >> > > − >> > > <wsdl:port name="WpsServiceUTSOAP11port_http" >> > > binding="tns:WpsServiceUTSOAP11Binding"> >> > > <soap:address location="http://callisto:6666/soap/WpsServiceUT"/> >> > > </wsdl:port> >> > > >> > > Is there a way to configure this behavior, as we have a different >> public >> > > domain name to access the service, that too through https? >> > > >> > > Balaji >> > > >> > > >> > > >> > >> > -- >> > View this message in context: >> http://www.nabble.com/Synapse-proxy-service-changes-service-address-location-tf4209274.html#a12041781 >> > Sent from the Synapse - Dev mailing list archive at Nabble.com. >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> -- >> Paul Fremantle >> Co-Founder and VP of Technical Sales, WSO2 >> OASIS WS-RX TC Co-chair >> >> blog: http://pzf.fremantle.org >> [EMAIL PROTECTED] >> >> "Oxygenating the Web Service Platform", www.wso2.com >> > > > -- > Paul Fremantle > Co-Founder and VP of Technical Sales, WSO2 > OASIS WS-RX TC Co-chair > > blog: http://pzf.fremantle.org > [EMAIL PROTECTED] > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Synapse-proxy-service-changes-service-address-location-tf4209274.html#a12053305 Sent from the Synapse - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
