Saita proxy na Spring-WS 4.1 da HttpComponents 5

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);

Yi amfani da wannan mai aikawa akan template da ke akwai kafin kira, tare da kiyaye URI na sabis, marshaller da sauran saitunan. Wannan Spring-WS 4.1.0 ne tare da Apache HttpClient 5. Idan samfurin yana nufin sabis ɗin SOAP na jama'a da aka yarda ba tare da tabbatarwar proxy ba, adireshin HTTP daga jerin proxy na HTTP zai iya cika proxy na mai keɓantawa.

withDefaults yana riƙe da mai shiga tsakani wanda ke cire Content-Length da Transfer-Encoding da SOAP ke bayarwa kafin Apache ya ƙirƙiri tsarin HTTP. Ƙara mai keɓantawar proxy a wurin yana hana maye gurbin wannan haɗin gwiwa da ɗanyen abokin ciniki. Don abokin ciniki na Apache da aka gina daban, riƙe mai shiga tsakani na cire kai na Spring-WS.

Daidaita imports da ƙirƙirar mai aikawa. Tsofaffin misalai da HttpComponentsMessageSender/org.apache.http suna amfani da Apache 4, ba wannan SimpleHttpComponents5MessageSender da mu'amalar HttpHost ba.

Riƙe mai aikawa da aka ƙirƙira da hannu tsawon rayuwar abokin ciniki na SOAP sannan ka shirya lalata shi na yau da kullum bayan haka. Bean da Spring ke sarrafawa zai iya amfani da zagayowar rayuwar kwantena. Sauran samfura da ke riƙe da sauran masu aikawa suna kiyaye nasu tsarin sufuri.