[JBoss JIRA] Created: (JBESB-3467) Propagate http-client-proeprties to SOAPProxyWsdlLoader.newLoader
by Kevin Conner (JIRA)
Propagate http-client-proeprties to SOAPProxyWsdlLoader.newLoader
-----------------------------------------------------------------
Key: JBESB-3467
URL: https://jira.jboss.org/browse/JBESB-3467
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.7 CP2
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.7 CP3
SOAPProxyWsdlLoader.newLoader does not use the correct configuration when invoked from SOAPProxy or SOAPProxyWsdlContractPublisher.. As a consequence it has no visibility of any http-client-property elements that are configured on the action.
This should retain current functionality as much as possible, only allowing changes to the WSDL configuration if configured.
There will be two mechanisms that can be used to configure the WSDL access through the SOAPProxy use case
- introduce wsdl-http-client-property elements for explicit configuration of the WSDL http client
- introduce a "wsdlUseHttpClientProperties" property so that the http-client-property elements can also be used
wsdl-http-client-property will override http-client-property.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBESB-3456) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
by Kevin Conner (JIRA)
AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3456
URL: https://jira.jboss.org/browse/JBESB-3456
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: Kevin Conner
Fix For: 4.9 CP1
If you set your config like this:
<action ... class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">
...
<property name="http-client-properties">
<http-client-property name="http.method.retry-handler" value="com.foobar.MyRetryHandler"/>
</property>
or like this:
<action ... class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">
...
<property name="file" value="http-client.properties"/>
http-client.properties:
http.method.retry-handler=com.foobar.MyRetryHandler
, your custom retry handler is not picked up. This is NOT a bug in SOAPProxy.
The bug is in both POSTHttpMethodFactory and GETHttpMethodFactory, where in the setConfiguration(ConfigTree):void method, the http-client-properties that are available in the passed-in ConfigTree are not set into the HttpMethod's HttpMethodParams.
What should happen is that ANY property that starts with "http.method." should be set into the HttpMethodParams.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBESB-3085) Loading of DRL Files in ContentBasedRouter
by Fernando Ribeiro (JIRA)
Loading of DRL Files in ContentBasedRouter
------------------------------------------
Key: JBESB-3085
URL: https://jira.jboss.org/jira/browse/JBESB-3085
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Content Based Routing
Affects Versions: 4.7
Reporter: Fernando Ribeiro
Unlike XsltAction, for example, ContentBasedRouter tries to find the template file in the file system before loading it from the classpath.
// Get the properties file stream...
if (ruleSetFile.exists()) {
try {
ruleStream = new FileInputStream(ruleSetFile);
} catch (FileNotFoundException e) {
throw new MessageRouterException("Unable to open rule properties file '" + ruleSetFile.getAbsolutePath() + "'.", e);
}
lastLoaded = ruleSetFile.lastModified();
} else {
ruleStream = ClassUtil.getResourceAsStream(ruleSetConfig, AbstractPropertyRulesRouter.class);
}
(from AbstractPropertyRulesRouter.java)
It is an easy miss because it is the only parameter that can't begin with "/".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months
[JBoss JIRA] Created: (JBESB-3434) AS4 duplicate jars on deployment
by Kevin Conner (JIRA)
AS4 duplicate jars on deployment
--------------------------------
Key: JBESB-3434
URL: https://jira.jboss.org/browse/JBESB-3434
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Build and Release
Affects Versions: 4.8
Reporter: Kevin Conner
Fix For: 4.9
./server/default/deploy/jbossesb.sar/lib/xpp3_min-1.1.3.4.O.jar ./server/default/deploy/jbrules.esb/xpp3_min-1.1.4c.jar
Should use the xpp3_min-1.1.4c.jar but have it in jbossesb.sar/lib
./server/default/deploy/jbossesb.sar/lib/stax-api-1.0.1.jar ./server/default/deploy/jbossesb.sar/lib/stax-api-1.0-2.jar
Should be stax-api.1.0.1.jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 8 months