January 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3035) A one-way message that throws exception should not return HTTP code 500

by Kevin Conner (JIRA)

A one-way message that throws exception should not return HTTP code 500 ----------------------------------------------------------------------- Key: JBESB-3035 URL: https://jira.jboss.org/jira/browse/JBESB-3035 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-2862) Add support for XPath based routing using SXC

by Tom Fennelly (JIRA)

Add support for XPath based routing using SXC --------------------------------------------- Key: JBESB-2862 URL: https://jira.jboss.org/jira/browse/JBESB-2862 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Tom Fennelly Fix For: 4.8 Use the existing XPathRouter and RegexRouter impls as a reference. -- 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

14 years, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-1946) Soapclient ognl soapenc:array support

by Joakim Sandström (JIRA)

Soapclient ognl soapenc:array support ------------------------------------- Key: JBESB-1946 URL: https://jira.jboss.org/jira/browse/JBESB-1946 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Joakim Sandström The current ognl implementation doesn't handle the following response correctly. Only the last findBySomethingReturn item is returned. i.e. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <ns1:findBySomethingResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://mydomain"> <findBySomethingReturn soapenc:arrayType="ns2:customer[2]" xsi:type="soapenc:Array" xmlns:ns2="urn:sys" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"> <findBySomethingReturn xsi:type="ns2:customer"> <id xsi:type="xsd:int">1</id> <name xsi:type="xsd:string">one</name> </findBySomethingReturn> <findBySomethingReturn xsi:type="ns2:customer"> <id xsi:type="xsd:int">2</id> <name xsi:type="xsd:string">two</name> </findBySomethingReturn> </findBySomethingReturn> </ns1:findBySomethingResponse> </soapenv:Body> </soapenv:Envelope> -- 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

14 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2556) Character corruption using SOAPClient (SOAPUI)

by Theodore S (JIRA)

Character corruption using SOAPClient (SOAPUI) ---------------------------------------------- Key: JBESB-2556 URL: https://jira.jboss.org/jira/browse/JBESB-2556 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Environment: any Reporter: Theodore S When using SOAPUI using International characters can lead to character corruption. How to reproduce: Send chinese characters in the WS request to a webservice endpoint using the SOAPUI integration in JBossESB. Fix: In class org.jboss.soa.esb.actions.soap.SOAPClient change line 462: post.setRequestEntity(new StringRequestEntity(request)); to StringRequestEntity requestEntity = new StringRequestEntity(request,"text/xml","UTF-8"); post.setRequestEntity(requestEntity); -- 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

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1553) SOAPClient action remappes objects with null strings to empty strings

by Jiri Pechanec (JIRA)

SOAPClient action remappes objects with null strings to empty strings --------------------------------------------------------------------- Key: JBESB-1553 URL: http://jira.jboss.com/jira/browse/JBESB-1553 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP2 Use webservice_consumer2 quickstart and use the attached files - contains enhanced equals and toString defintions. Make sure that option1 is used. The object with following contents is sent to processing to ivoke web service id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = null But in the web service processing method the contents is id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = The difference is in shipTo property which was set tu null on the input but comes to web service as empty string. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
21
0 / 0

[JBoss JIRA] Created: (JBESB-3088) Wrong Parameter Name for soapUI SOAP Client Action

by Fernando Ribeiro (JIRA)

Wrong Parameter Name for soapUI SOAP Client Action -------------------------------------------------- Key: JBESB-3088 URL: https://jira.jboss.org/jira/browse/JBESB-3088 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.7 Reporter: Fernando Ribeiro On page 128 of the Programmers Guide, "operation" is mistaken by "SOAPAction", which is at http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/services/.... -- 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

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2905) FtpImpl timeout global and not always respected

by Tom Eicher (JIRA)

FtpImpl timeout global and not always respected ----------------------------------------------- Key: JBESB-2905 URL: https://jira.jboss.org/jira/browse/JBESB-2905 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.6, 4.5 Reporter: Tom Eicher org.jboss.internal.soa.esb.util.FtpImpl does look for a property org.jboss.soa.esb.ftp.timeout in jbossesb.sar/jbossesb-properties.xml, however: it does so only in 1 out of 3 constructors! ;-) code "String timeout = ModulePropertyManager..." should be moved from the "public FtpImpl (FTPEpr p_oP)" to the "protected void initialize (boolean bConnect)". other parameters in the 3 constructor should also be checked if they are respected in all three cases. Also: - "infinite" is not so good a default, as the thread will hang forever in case of firewall issues (I have one 48hrs old now ;-) even a ridiculous long one like 6hrs woule be better...("_timeout = 0;" in 2 places) - please add "<property name="org.jboss.soa.esb.ftp.timeout" value="60000"/>" to the default jbossesb-properties.xml so that people may know that this setting exists - please also allow configuration of timeout from ConfigTree (method "checkParams()" and Constant in "RemoteFileSystem") and from FileEpr. (and then add to doc ;-) Cheers & kind regards, Tom. -- 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

14 years, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JBESB-3084) Customize Context Root of HTTP Gateway

by Fernando Ribeiro (JIRA)

Customize Context Root of HTTP Gateway -------------------------------------- Key: JBESB-3084 URL: https://jira.jboss.org/jira/browse/JBESB-3084 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Fernando Ribeiro It would be nice to be able to customize the context root in jboss-esb.xml, just like in jboss-web.xml. http://fernandoribeiro.eti.br/2009/09/13/how-to-change-the-context-root-i... -- 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

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-3038) spring_aop QS does not work with signed JARs

by Kevin Conner (JIRA)

spring_aop QS does not work with signed JARs -------------------------------------------- Key: JBESB-3038 URL: https://jira.jboss.org/jira/browse/JBESB-3038 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2981) Support textual file contents in file and remote gateways

by Kevin Conner (JIRA)

Support textual file contents in file and remote gateways --------------------------------------------------------- Key: JBESB-2981 URL: https://jira.jboss.org/jira/browse/JBESB-2981 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 The current implementation of these gateways generates the contents of the message as a byte[], as they must assume that they are binary. We should add the ability to create textual representations, instead of binary ones, by converting the byte[] to a String using a specified character set. -- 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

14 years, 9 months

4
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2010