Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

OpenHub framework provides own customized solution as CloseableHttpComponentsMessageSender, which uses the Apache HttpComponents HttpClient. Use that if you need more advanced and easy-to-use functionality (such as authentication, HTTP connection pooling, and so forth).

The following example shows how to configure this component, and to use Apache HttpClient to authenticate using HTTP authentication with connection poolling per host:

<bean id="billingSender" class="org.openhubframework.openhub.common.ws.transport.http.CloseableHttpComponentsMessageSender">
 <constructor-arg index="0" value="true"/> <!-- use Preemptive Auth-->
 <property name="credentials">
  <bean class="org.apache.http.auth.UsernamePasswordCredentials">
   <constructor-arg index="0" value="${billing.user}"/>
   <constructor-arg index="1" value="${billing.password}"/>
  </bean>
 </property>
 <property name="maxTotalConnections" value="${billing.maxTotalConnections}"/>
 <property name="defaultMaxPerHost" value="${billing.maxTotalConnections}"/>
 <property name="maxConnectionsPerHost">
  <props>
   <prop key="${billing.uri}">${billing.maxTotalConnections}</prop>
  </props>
 </property>
 <property name="connectionTimeout" value="${billing.connectionTimeout}"/>
 <property name="readTimeout" value="${billing.readTimeout}"/>
</bean>

OpenHub 2.1: class changed package, from org.openhubframework.openhub.core.common.ws.transport.http to org.openhubframework.openhub.common.ws.transport.http

  • No labels