Ukulungisa i-proxy ye-Spring-WS 4.1 nge-HttpComponents 5
Ngenisa ngokwezifiso i-HttpComponents5 client factory ye-Spring-WS 4.1 bese uxhuma isithumeli esikhishiwe ku-WebServiceTemplate.
import org.apache.hc.core5.http.HttpHost;
import org.springframework.ws.transport.http.HttpComponents5ClientFactory;
import org.springframework.ws.transport.http.SimpleHttpComponents5MessageSender;
var factory = HttpComponents5ClientFactory.withDefaults();
factory.addClientBuilderCustomizer(builder ->
builder.setProxy(new HttpHost("http", "proxy.example", 8080)));
var sender = new SimpleHttpComponents5MessageSender(factory);
template.setMessageSender(sender);Sebenzisa lesi sithumeli ku-template okhoyo ngaphambi kokushaya ucingo, ugcine i-URI yensizakalo, i-marshaller nezinye izilungiselelo. Lokhu yi-Spring-WS 4.1.0 ne-Apache HttpClient 5. Uma ithempulethi iqondise insizakalo yomphakathi evunyelwe ye-SOAP ngaphandle kokuqinisekiswa kwe-proxy, ikheli le-HTTP elivela kuhlu lwe-proxy ye-HTTP lingagcwalisa i-proxy yesilungisi.
withDefaults igcina isixhumanisi esisusa i-Content-Length ne-Transfer-Encoding ezihlinzekwa yi-SOAP ngaphambi kokuthi i-Apache yakhe ukwakheka kwe-HTTP. Ukwengeza isilungisi se-proxy lapho kugwema ukuthi lokho kuhlangana kushintshwe iklayenti elingenalutho. Kuklayenti le-Apache elakhiwe ngokwahlukile, gcina isixhumanisi sokususa izihloko se-Spring-WS.
Qondanisa ama-import nokukhiqizwa kwesithumeli. Izibonelo ezindala ezine-HttpComponentsMessageSender/org.apache.http zisebenzisa i-Apache 4, hhayi le SimpleHttpComponents5MessageSender kanye ne-interface ye-HttpHost.
Gcina isithumeli esakhiwe ngesandla phakathi nokuphila konke kweklayenti le-SOAP bese uhlela ukuqedwa kwaso okuvamile ngemuva kwalokho. I-bean ephethwe yi-Spring ingasebenzisa umjikelezo wempilo wesitsha. Amanye amathempulethi agcina ezinye izithumeli agcina ukulungisa kwawo kwezokuthutha.