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.
