August 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1908) DslHelper is using weak hash map as a cache

by Kevin Conner (JIRA)

DslHelper is using weak hash map as a cache ------------------------------------------- Key: JBESB-1908 URL: https://jira.jboss.org/jira/browse/JBESB-1908 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.4 CP1 The DslHelper is using a weak hashmap as a cache of xpath evaluation results and is also unlikely to work in a MT environment. -- 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

16 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1915) tools/console/management-esb/build.xml always refers to the "default" profile

by Julian Coleman (JIRA)

tools/console/management-esb/build.xml always refers to the "default" profile ----------------------------------------------------------------------------- Key: JBESB-1915 URL: https://jira.jboss.org/jira/browse/JBESB-1915 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.4 Environment: SOA embedded 4.3.0 (pre-release) Reporter: Julian Coleman Priority: Minor See SOA-582. -- 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

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1921) The replyToOriginator initialisation in NewProcessIntanceFacade does not handle missing values

by Kevin Conner (JIRA)

The replyToOriginator initialisation in NewProcessIntanceFacade does not handle missing values ---------------------------------------------------------------------------------------------- Key: JBESB-1921 URL: https://jira.jboss.org/jira/browse/JBESB-1921 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 The code should test for null and remove any entries already present. -- 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

16 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1920) Implement Content Based Detour action

by Joakim Sandstr?m (JIRA)

Implement Content Based Detour action ------------------------------------- Key: JBESB-1920 URL: https://jira.jboss.org/jira/browse/JBESB-1920 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 Reporter: Joakim Sandstr?m I need a content based router which implements the detour pattern as described at http://www.enterpriseintegrationpatterns.com/Detour.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

16 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1917) Get rid of transformation console from main console

by Tom Fennelly (JIRA)

Get rid of transformation console from main console --------------------------------------------------- Key: JBESB-1917 URL: https://jira.jboss.org/jira/browse/JBESB-1917 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x Sounds like that thing is still hanging around :-( I thought it was removed ago. >From recollection, it wasa not so easy to remove because it was intertwined with the other management console tooling. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1916) Quickstart "business_ruleservice_stateful": Change quickstart scenario to a non-conversation usecase

by Tom Fennelly (JIRA)

Quickstart "business_ruleservice_stateful": Change quickstart scenario to a non-conversation usecase ---------------------------------------------------------------------------------------------------- Key: JBESB-1916 URL: https://jira.jboss.org/jira/browse/JBESB-1916 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x At the moment, the quickstart uses the BusinessRulesService in a conversation type scenario where the Service accumulates the total spend for a customer over multiple orders. This is fine for demo, but will not work with the BusinessRulesService in a multi-conversation type usecase (multiple cutsomers etc) because it only uses a single session model - would need to support a multi session model to manage multiple conversations. Even with a proper conversational model (multi-session), the usecase in this example would be a bit bogus because the separate orders would most likely be part of different conversations (i.e. different sessions). -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1902) The state of stateful rule services is shared between services

by Jiri Pechanec (JIRA)

The state of stateful rule services is shared between services -------------------------------------------------------------- Key: JBESB-1902 URL: https://jira.jboss.org/jira/browse/JBESB-1902 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing, Documentation Affects Versions: 4.4 Reporter: Jiri Pechanec Assignee: Daniel Bevenius Fix For: 4.4 CP1 The stateful working session is stored in the cache under the resource from which the rule base was build. It means that two services that are using the same rule resource location are using the same working memory. Although it allows to share state between services it can prevent the reuse of the source code in multiple services. This behaviour should be documented. -- 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

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1905) The stateful working memory is used concurrently by multiple threads

by Jiri Pechanec (JIRA)

The stateful working memory is used concurrently by multiple threads -------------------------------------------------------------------- Key: JBESB-1905 URL: https://jira.jboss.org/jira/browse/JBESB-1905 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Blocker Fix For: 4.4 CP1 The stateful rule service should use only one thread. It is not clear from Drools documentation but my guess is that working memory is single-threaded working structure. This has to be verified with Drools team. If so this limitatation has to be clearly stated in documentation and enforced in code. It can also put JBESB-1902 into different light. -- 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

16 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1907) Race condition when creating stateful working memory

by Jiri Pechanec (JIRA)

Race condition when creating stateful working memory ---------------------------------------------------- Key: JBESB-1907 URL: https://jira.jboss.org/jira/browse/JBESB-1907 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Critical Fix For: 4.4 CP1 If more than one thread is used the following code is buggy private StatefulSession getStatefulSession( final RuleBase ruleBase ) { final StatefulSession[] statefulSessions = ruleBase.getStatefulSessions(); boolean existingSession = statefulSessions != null && statefulSessions.length > 0; return existingSession ? statefulSessions[0] : ruleBase.newStatefulSession(); } It can lead into initiation and use of two working memories for the first messages coming. -- 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

16 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1911) ObjectMapper does not easily allow to use MVEL expressions on object in default slot

by Jiri Pechanec (JIRA)

ObjectMapper does not easily allow to use MVEL expressions on object in default slot ------------------------------------------------------------------------------------ Key: JBESB-1911 URL: https://jira.jboss.org/jira/browse/JBESB-1911 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Minor Fix For: 4.x The MVEL expressions are used only if path contains the name of the slot in message body. This lead to ugly addressing like body.'org.jboss.soa.esb.message.defaultEntry'.<mvelpath> which moreover depends on implementation internals. It would be useful to provide standardized access like body..<mvelpath> or body.$default.<mvelpath> -- 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

16 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2008