May 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3312) Configure FTP's control channel encoding

by jarkko Lietolahti (JIRA)

Configure FTP's control channel encoding ---------------------------------------- Key: JBESB-3312 URL: https://jira.jboss.org/jira/browse/JBESB-3312 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.8 Reporter: jarkko Lietolahti Currently there's no way to configure the encoding of FTP's control channel. There're cases where this is required for correct action. Like sending files which have non-ascii characters in filenames. The required functionality is there in Apache Commons NET, but there's no way to relay proper configuration to it. http://commons.apache.org/net/api/org/apache/commons/net/ftp/FTPClient.html -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3308) ReplyTo EPR must be manually reset after Aggregator action is used

by David van Balen (JIRA)

ReplyTo EPR must be manually reset after Aggregator action is used ------------------------------------------------------------------ Key: JBESB-3308 URL: https://jira.jboss.org/jira/browse/JBESB-3308 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: David van Balen The ESB depends on the message's replyTo to know where to send a reply in a RequestResponse service. However, the Aggregator action makes no attempt to preserve the replyTo when it creates an aggregate message for a series. In most cases, I would think the replyTo on the aggregated messages would be the same, so adding it onto the resulting aggregated message would seem like a good idea. Otherwise, it has to be handled manually in the assembler action. -- 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, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBESB-3276) soapui client fails to load multiple interfaces if authentication required

by Kevin Conner (JIRA)

soapui client fails to load multiple interfaces if authentication required -------------------------------------------------------------------------- Key: JBESB-3276 URL: https://jira.jboss.org/jira/browse/JBESB-3276 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP1 Reporter: Kevin Conner The reason for this is that only the last interface contains the wsdl context loaded using our httpclient, forcing prior interfaces to reload using the UrlWsdlLoader. This does not have knowledge of the authentication as we place it on the httpclient and it instantiates its own httpclient. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3309) Aggregator meta data in properties

by Kevin Conner (JIRA)

Aggregator meta data in properties ---------------------------------- Key: JBESB-3309 URL: https://jira.jboss.org/jira/browse/JBESB-3309 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 CP3 Reporter: Kevin Conner Fix For: 4.4 CP5 The MessageMulticaster creates an aggregation id and stores this value in message properties. Normally this does not prove to be an issue but when using invm transport it may cause issues. When the message is sent to multiple services, using pass by reference semantics, then all services will see the *same* properties and may, depending on timing, see the same aggregation id. The aggregation value should really be in the message context as this section is always duplicated when creating a reference, never shared. The problem we face is that users may already be referencing the property, especially if they are creating a fresh response message, so we need to think about handling this. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3291) wrong description of JMSEpr.messageSelector

by Marcel Sebek (JIRA)

wrong description of JMSEpr.messageSelector ------------------------------------------- Key: JBESB-3291 URL: https://jira.jboss.org/jira/browse/JBESB-3291 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Marcel Sebek All constructors of JMSEpr have description of the messageSelector the same as connectionFactory ("reference to the connection factory"). -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3289) BpmProcessor documentation anarchy

by Marcel Sebek (JIRA)

BpmProcessor documentation anarchy ---------------------------------- Key: JBESB-3289 URL: https://jira.jboss.org/jira/browse/JBESB-3289 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Marcel Sebek The documentation of BpmProcessor is misleading. In the programmers guide, there is the following: " The following jBPM commands have been implemented: - NewProcessInstanceCommand - StartProcessCommand - CancelProcessInstanceCommand - GetProcessInstanceVariablesCommand " The correct version is StartProcessInstanceCommand. A few lines bellow, there is NewProcessInstance-Command (the dash should probably not be there). Also SignalProcessInstanceCommand is mentioned but that command has been removed. Instead of "processdefinition", there should be "process-definition-name". In ServicesGuide, there is also a note about SignalProcessInstanceCommand and the "processdefinition" is there too. There may be more occurrences of these inconsistencies, I've mentioned just the most obvious. -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3298) Update H2 version

by Gary Brown (JIRA)

Update H2 version ----------------- Key: JBESB-3298 URL: https://jira.jboss.org/jira/browse/JBESB-3298 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.8 Reporter: Gary Brown The current version uses h2-1.0.68.jar, which is placed in the server/default/lib folder on deployment to the app server. Could you update the version to a more recent version, e.g. 1.2.124 or higher, as the older version is causing concurrent update exceptions when used with riftsaw. -- 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, 5 months

3
3
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, 5 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3281) EBWS: Add support for schemas that exist in jarsin

by Daniel Bevenius (JIRA)

EBWS: Add support for schemas that exist in jarsin -------------------------------------------------- Key: JBESB-3281 URL: https://jira.jboss.org/jira/browse/JBESB-3281 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Daniel Bevenius -- 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, 5 months

2
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2010