March 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2110) Move LogicalEPRUnitTest away from files

by Kevin Conner (JIRA)

Move LogicalEPRUnitTest away from files --------------------------------------- Key: JBESB-2110 URL: https://jira.jboss.org/jira/browse/JBESB-2110 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.4 Reporter: Kevin Conner The test relies on the existence of a file for output, leading to an obvious race between creating/reading. We should change this test to pass the messages via an MBean as in the other tests. -- 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, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1715) Add support for annotated actions

by Kevin Conner (JIRA)

Add support for annotated actions --------------------------------- Key: JBESB-1715 URL: http://jira.jboss.com/jira/browse/JBESB-1715 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.4 -- 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

15 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-2874) Deployers do not cleanly represent dependencies

by Kevin Conner (JIRA)

Deployers do not cleanly represent dependencies ----------------------------------------------- Key: JBESB-2874 URL: https://jira.jboss.org/jira/browse/JBESB-2874 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 The deployers create a separate object to represent the ESB deployment, expressing the contained dependencies, but any forced restart of this object (due to dependencies) does not redo any of the work contained in the deployer. We now have a lot of work which, as a consequence, misses out on this process. - ebws - http gateway - property substitution We need to move all this functionality into a separate object which can cleanly take part in the dependency process. -- 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, 9 months

3
13
0 / 0

[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

15 years, 9 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

15 years, 9 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

15 years, 10 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

15 years, 10 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

15 years, 10 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3177) In FtpImpl.java also setSoTimeout(_timeout); in initialize(boolean bConnect)

by jarkko Lietolahti (JIRA)

In FtpImpl.java also setSoTimeout(_timeout); in initialize(boolean bConnect) ---------------------------------------------------------------------------- Key: JBESB-3177 URL: https://jira.jboss.org/jira/browse/JBESB-3177 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: jarkko Lietolahti Currently FtpImpl.java (and the others) only set DataTimeout on m_oConn. We're seeing firewall issues where this is not enough and we need SoTimeout for the socket in order to avoid infinite waiting during __getReply(); So also call m_oConn.setSoTimeout(_timeout); Aka; if (_timeout > 0) { m_oConn.setDataTimeout(_timeout); // added by jarkko lietolahti, 9.2.2010 to address hanging replies from server m_oConn.setSoTimeout(_timeout); } -- 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, 10 months

4
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2010