[
https://issues.apache.org/jira/browse/CXF-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CXF-3621:
-----------------------------
Fix Version/s: NeedMoreInfo
Assignee: Daniel Kulp
I'd definitely need to see a testcase for this. The problem with the spring
context defined in that nabble post is that nowhere does it associate the
http-conf or anything else in that context with a Bus. Thus, the config
wouldn't be picked up at all. The best way to do that would be to <import
resource="classpath:META-INF/cxf/cxf.xml"/> and then likely add <property
name="bus" ref="cxf"/> to the JaxWsProxyFactoryBean to make sure they are
wired together properly.
> Http-conduit:conf does not apply to JaxWsProxyFactoryBean bean. Works for
> 2.3.3.
> --------------------------------------------------------------------------------
>
> Key: CXF-3621
> URL: https://issues.apache.org/jira/browse/CXF-3621
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.4.1
> Environment: Tomcat + CXF 2.4.1
> Reporter: Marc Elbichon
> Assignee: Daniel Kulp
> Fix For: 2.3.3, NeedMoreInfo
>
>
> When using this configuration with CXF 2.3.3, timeout is triggered, but not
> with CXF 2.4.1
> {code:xml}
> <http-conf:conduit name="*.http-conduit" >
> <http-conf:client ConnectionTimeout="1000" ReceiveTimeout="1000"
> AllowChunking="false" />
> </http-conf:conduit>
> <bean id="MDMClientproxyFactory"
> class="org.apache.cxf.jaxws.JaxWsProxyFactoryBean">
> <property name="serviceClass" value="xxx.PartyService"/>
> <property name="address" value="${mdm.service.url}"/>
> </bean>
> {code}
> Looks like
> http://cxf.547215.n5.nabble.com/Setting-Http-conduit-using-spring-configuration-file-td2644363.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
