June 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1770) insert-timestamp-column parameter ignored in sql-message-filter

by Stefano Maestri (JIRA)

insert-timestamp-column parameter ignored in sql-message-filter --------------------------------------------------------------- Key: JBESB-1770 URL: http://jira.jboss.com/jira/browse/JBESB-1770 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.3 Reporter: Stefano Maestri Assigned To: Stefano Maestri The parameter is ignored for a little bug in SqlTableGatewayListener class -- 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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1833) SQLCourier BLOB/CLOB support does not work on Oracle

by Jiri Pechanec (JIRA)

SQLCourier BLOB/CLOB support does not work on Oracle ---------------------------------------------------- Key: JBESB-1833 URL: http://jira.jboss.com/jira/browse/JBESB-1833 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3, 4.3 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP4, 4.4 The BLOB support, added as part of JBESB-1690, is not sufficient for postgres. The issue lies in the creation of the table entries as the code uses the statement.setObject method to initialise the parameter. We need to change this to use the setCharacterStream/setBinaryStream equivalents. -- 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

17 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1834) SQLCourier BLOB support does not work on mysql

by Jiri Pechanec (JIRA)

SQLCourier BLOB support does not work on mysql ---------------------------------------------- Key: JBESB-1834 URL: http://jira.jboss.com/jira/browse/JBESB-1834 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3, 4.3 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP4, 4.4 The BLOB support, added as part of JBESB-1690, is not sufficient for postgres. The issue lies in the creation of the table entries as the code uses the statement.setObject method to initialise the parameter. We need to change this to use the setCharacterStream/setBinaryStream equivalents. -- 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

17 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1805) SQLCourier BLOB support does not work on postgres

by Kevin Conner (JIRA)

SQLCourier BLOB support does not work on postgres ------------------------------------------------- Key: JBESB-1805 URL: http://jira.jboss.com/jira/browse/JBESB-1805 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 CP3, 4.3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP4, 4.4 The BLOB support, added as part of JBESB-1690, is not sufficient for postgres. The issue lies in the creation of the table entries as the code uses the statement.setObject method to initialise the parameter. We need to change this to use the setCharacterStream/setBinaryStream equivalents. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1808) business_rules_service QS is missing an action

by Jaroslaw Kijanowski (JIRA)

business_rules_service QS is missing an action ---------------------------------------------- Key: JBESB-1808 URL: http://jira.jboss.com/jira/browse/JBESB-1808 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP2 Reporter: Jaroslaw Kijanowski >From the readme file in the business_rules_service QS: The customer status is actually set in the jboss-esb.xml via the SetupMessage action since it is not provided with the inbound XML. There's no SetupMessage which would initialize the status of a customer. This has an impact on business rules, which won't fire (besides the logging rules), because they depend on the status value of a customer. Moreover when deploying I get this: 15:07:15,372 INFO [ContentBasedWiretap] Missing or empty destination list - This action class won't have any effect 15:07:15,372 INFO [ContentBasedWiretap] Missing or empty destination list - This action class won't have any effect I guess it's because there are two business rules files, both not used for routing... But that's already filed: JBESB-986 -- 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

17 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1856) Update ServicesGuide section, "Content Based Routing using Smooks". The Smooks configuration example is missing.

by Daniel Bevenius (JIRA)

Update ServicesGuide section, "Content Based Routing using Smooks". The Smooks configuration example is missing. ---------------------------------------------------------------------------------------------------------------- Key: JBESB-1856 URL: http://jira.jboss.com/jira/browse/JBESB-1856 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.4 On page 43, the is this line: "The Smooks configuration for the above example would look as follows." But there is now configuration example in below this. This needs to be re-added as the next section describes the configuration and without the example make this difficult to understand. -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1804) Handle wild card binding address

by Kevin Conner (JIRA)

Handle wild card binding address -------------------------------- Key: JBESB-1804 URL: http://jira.jboss.com/jira/browse/JBESB-1804 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 CP3, 4.3 Reporter: Kevin Conner Fix For: 4.2.1 CP4, 4.4 At present we default to jboss.bind.address for the jndi-url (in jbossesb-properties.xml) but there is an issue when the ANY address is used with -b Starting the server using -b 0.0.0.0 will cause our EPRs to specify an IP address of 0.0.0.0. We should use our own property, as other projects do, and have this initialised using ServerConfigUtil.fixRemoteAddress. -- 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

17 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1622) Need to make sure that Message ID is not overwritten by JMS message ID

by Tom Cunningham (JIRA)

Need to make sure that Message ID is not overwritten by JMS message ID ---------------------------------------------------------------------- Key: JBESB-1622 URL: http://jira.jboss.com/jira/browse/JBESB-1622 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 CP1 Reporter: Tom Cunningham Need to make sure that the message ID is not overwritten by the JMS message ID. The message ID is going to be used to correlate reply-to messages and link message metadata - we're going to need them to be consistent so for monitoring. -- 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

17 years, 9 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-1703) https_2way_ssl quickstart not runnable

by Julian Coleman (JIRA)

https_2way_ssl quickstart not runnable -------------------------------------- Key: JBESB-1703 URL: http://jira.jboss.com/jira/browse/JBESB-1703 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Environment: RHEL 5 Reporter: Julian Coleman The https_2way_ssl quickstart doesn't run out of the box. First, it doesn't deploy correctly, as the ESB dependency is wrong. Second, an extra "/" is needed to find the keystore. -- 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

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1729) EJBProcessor doing JNDI lookup on every call - could cache

by Tom Fennelly (JIRA)

EJBProcessor doing JNDI lookup on every call - could cache ---------------------------------------------------------- Key: JBESB-1729 URL: http://jira.jboss.com/jira/browse/JBESB-1729 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Reporter: Tom Fennelly -- 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

17 years, 9 months

2
3
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 2008