January 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3892) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3892?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3892. ----------------------------------- Assignee: Tom Cunningham Resolution: Done > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3892 > URL: https://issues.jboss.org/browse/JBESB-3892 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3892) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3892?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3892: ---------------------------------- Component/s: Rosetta > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3892 > URL: https://issues.jboss.org/browse/JBESB-3892 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3892) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3892?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3892: ---------------------------------- Affects Version/s: 4.11 > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3892 > URL: https://issues.jboss.org/browse/JBESB-3892 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.11 > Reporter: Tom Cunningham > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3892) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3892?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3892: ---------------------------------- Description: In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. The following variations were tested: <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3892 > URL: https://issues.jboss.org/browse/JBESB-3892 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tom Cunningham > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3892) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3892: ------------------------------------- Summary: PropertySubstituter not expanding properties in notifications Key: JBESB-3892 URL: https://issues.jboss.org/browse/JBESB-3892 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3707) Cached resource creation is not synchronized in SOAPUIClientService

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3707?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3707: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> made a comment on [bug 781074|https://bugzilla.redhat.com/show_bug.cgi?id=781074] GSS is marking this one 'gss_prioritized' so we can track it via BZ views. We have customers requesting this fix, so we're glad it's accepted for 5.3.1. Thanks, Rick > Cached resource creation is not synchronized in SOAPUIClientService > ------------------------------------------------------------------- > > Key: JBESB-3707 > URL: https://issues.jboss.org/browse/JBESB-3707 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.10 > Reporter: Magesh Bojan > Assignee: Magesh Bojan > Fix For: 5.0 initial development > > > Wsdl and Smooks Resource cache creation are not synchronized and hence could lead to a race condition when the same resource is being created by multiple threads. > Fix is to synchronize the cached resource creation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2013