June 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3332) Provide support for HornetQ

by Kevin Conner (JIRA)

Provide support for HornetQ --------------------------- Key: JBESB-3332 URL: https://jira.jboss.org/browse/JBESB-3332 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.8 Reporter: Kevin Conner Priority: Blocker Fix For: 4.9 Support hornetq as an alternative provider. Need to test integration and selectively include the correct configuration. -- 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, 9 months

2
9
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-3328) Merge across JBESB_4_7_CP2_ER2 tag

by Kevin Conner (JIRA)

Merge across JBESB_4_7_CP2_ER2 tag ---------------------------------- Key: JBESB-3328 URL: https://jira.jboss.org/browse/JBESB-3328 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.8 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 -- 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, 9 months

1
8
0 / 0

[JBoss JIRA] Created: (JBESB-3292) Spring Integration needs to be updated to use SNOWDROP's VFSClassPathXmlApplicationContext

by Alex Deschapelles (JIRA)

Spring Integration needs to be updated to use SNOWDROP's VFSClassPathXmlApplicationContext ------------------------------------------------------------------------------------------ Key: JBESB-3292 URL: https://jira.jboss.org/jira/browse/JBESB-3292 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: Alex Deschapelles The current AbstractSpringAction uses the standard ClassPathXmlApplicationContext (line 208 in the jboss-spring.jar) This does not work when the spring config searches for resources using the classpath*: notation. To fix, replace the ClassPathXmlApplicationContext with VFSClassPathXmlApplicationContext from SNOWDROP. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-3275) SOAPClient may fail NTLM negotiations

by Kevin Conner (JIRA)

SOAPClient may fail NTLM negotiations ------------------------------------- Key: JBESB-3275 URL: https://jira.jboss.org/jira/browse/JBESB-3275 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP1 Reporter: Kevin Conner The soapui client may fail NTLM negotiations if no keep-alive is set on the connection. Some servers may respond with a directive to close each connection, which soapui honours. If this happens then each step of the NTLM negotiation will be handled over a separate connection and will fail. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBESB-3293) FtpImpl getFileListFromRemoteDir() bad suffix handling, listing subdir contents

by Tom Eicher (JIRA)

FtpImpl getFileListFromRemoteDir() bad suffix handling, listing subdir contents ------------------------------------------------------------------------------- Key: JBESB-3293 URL: https://jira.jboss.org/jira/browse/JBESB-3293 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.8, 4.7 CP1, 4.7, 4.6 Reporter: Tom Eicher - RemoteFileSystem.getFileListFromRemoteDir(p_sSuffix) is meant to return the listing of the files of the current directory. - however, due to the "suffix enforcing" in FtpImpl, even calls like "getFileListFromRemoteDir(null)" and "getFileListFromRemoteDir("")" will be executed as getFileListFromRemoteDir("*"), making this a FTP "NLST *" command. - (and "getFileListFromRemoteDir(".")" will be "getFileListFromRemoteDir("*.")"...) - now, when your target directory contains only one entry, and that entry is a file, the NLST will glob the "*" and return the listing of the subdir(!) - so, you will get unexpected results like "tmp/file1", "tmp/file2", when all you wanted was to receive the "tmp". - even when giving a suffix like "*.xml", this will return "tmp/file1.xml". - tested against Microsoft ftp server, but the behaviour is as expected, so will be identical with many ftp servers - fix: when no suffix given, call "listNames()", not "listNames("*")". - see also: FTPClient.listNames(String) docu, which says "The server may or may not expand glob expressions". For ftp servers not doing globbing, this means all downloads will fail. -- 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-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

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

15 years, 10 months

4
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2010