It should, yes. The client just sees the “published” url which would be the initial URL that you have there. From it’s standpoint, it grabs the wsdl from that, the address in the wsdl is that, etc…
What happens internally by the various apache servers and tomcats should be fine. HOWEVER, if you do something funky in an interceptor or in your code that grabs the HttpRequest or ServletContext or something and looks for a specific HOST header or something, that may not work as quite as expected as all would get the same (public) value. But that’s normal with HTTP in any clustered environment like that. Dan On Dec 3, 2013, at 2:50 PM, Faz <[email protected]> wrote: > Thanks a lot for getting onto this Dan, > > This options looks fine,though I have a question. If we have this set to the > published wsdl , will the load-balancing work as normal. > > For instance, will it work fine with the below criteria? > > If the WS is deployed to 2 different tomcat/weblogic servers which are in > the clustered mode and are resided on top of apache server, which inturn is > load-balanced . > > i.e, the initial URL will be like, https://mytest.services.com/ (main DNS) > > https://mytest.services.com/services/getservice (user request via client) > * |* > * | > |* > https://apache1/services/getservice https://apache2/services/getservice > [Apache server routing] > > * | |* > https://tomcat[1/2]/services/getservice > https://tomcat[3/4]/services/getservice > > *So as above the WS will be deployed to 4 tomcat servers, in this case what > would be the service deployed url / address and what would be the > publishedEndpointUrl? *Please provide your insights on this.... > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Load-balancing-SSL-WSDL-Java-tp5737320p5737331.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
