April 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-726) JCR Message repository does not support classification and delivery earmark

by Jiri Pechanec (JIRA)

JCR Message repository does not support classification and delivery earmark --------------------------------------------------------------------------- Key: JBESB-726 URL: http://jira.jboss.com/jira/browse/JBESB-726 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor JCR Message repository currently does not support classification and delivery flag. Proposed solution 1) Add special property under which the classification will be stored 2) Add special property under which delivery earmark will be stored 3) Implement all get<Collection> actions as JCR query and return the results -- 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, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1682) Fix helloworld_file_notifier QS

by Tom Cunningham (JIRA)

Fix helloworld_file_notifier QS ------------------------------- Key: JBESB-1682 URL: http://jira.jboss.com/jira/browse/JBESB-1682 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Fix the helloworld_notify_files QS so that it uses the new property substitution that was added in JBESB-1589. There's no longer any need to do the ant based token replacement in this QS. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1644) Create a task that illustrates the use of FaultTo

by Mark Little (JIRA)

Create a task that illustrates the use of FaultTo ------------------------------------------------- Key: JBESB-1644 URL: http://jira.jboss.com/jira/browse/JBESB-1644 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Mark Little Fix For: 4.3 -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-549) Automate war deployment for quickstarts

by Kevin Conner (JIRA)

Automate war deployment for quickstarts --------------------------------------- Key: JBESB-549 URL: http://jira.jboss.com/jira/browse/JBESB-549 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 We need to be able to automatically deploy the QSes into a war deployment. The main blocker for this issue is the new requirement to merge jboss-esb.xml configuration files. This is required because of the ESB internal services. -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-643) Add BRMS support to RuleService

by Jeff DeLong (JIRA)

Add BRMS support to RuleService -------------------------------- Key: JBESB-643 URL: http://jira.jboss.com/jira/browse/JBESB-643 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Jeff DeLong Assigned To: Mark Little Add BRMS support to the platform. In particular the capability to specify a rulesBase in the ruleService configuration and have the ruleService retrieve the ruleBase from the BRMS instead of creating ruleBase on the fly from drl / dsl files on the classpath. This will allow for better maintenance and management of the rules, as well as "hot" deployment on the rules. Note - I listed this under CBR as there is not a RuleService Component listed, however it applies to both CBR and RuleService. -- 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, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-550) ESB war deployment for websphere/weblogic

by Kevin Conner (JIRA)

ESB war deployment for websphere/weblogic ----------------------------------------- Key: JBESB-550 URL: http://jira.jboss.com/jira/browse/JBESB-550 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Optional Fix For: 4.2 Look at deploying the ESB war file into websphere/weblogic -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-645) Add support for decision tables to RuleServices

by Jeff DeLong (JIRA)

Add support for decision tables to RuleServices ----------------------------------------------- Key: JBESB-645 URL: http://jira.jboss.com/jira/browse/JBESB-645 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Jeff DeLong Assigned To: Mark Little The current ruleService does not appear to support Decision Tables. Decision Tables require the use of the SpreadsheetCompiler API to create a drl from a spreadsheet on the classpath. -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-644) Add support for both stateless and stateful RuleServices

by Jeff DeLong (JIRA)

Add support for both stateless and stateful RuleServices -------------------------------------------------------- Key: JBESB-644 URL: http://jira.jboss.com/jira/browse/JBESB-644 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Jeff DeLong Assigned To: Mark Little The current JBossRuleRouter (which currently implements the RuleService) uses StatefulSessions in a Stateless way. Which is fine in most cases). JBossRulesRouter creates a new workingMemory (StatefulSession), asserts facts, and should (although it does not currently, disponse of the workingMemory - See also JBESB-642. ). JBoss Rules support StatelessSessions. The need to dispose of workingMemory is eliminated if StatelessSessions are used. StatelessSession have some limitations compared to Stateful, but are designed for instance, for rule applications deployed as web services, where basically a single method needs to transfer all the data, create the workingMemory, assert the data (as a single object or list of objects) and fire the rules. CBR can be thought of as a stateless service. A single Message object is asserted into working memory, and the rules are fired. Many rule application will be like this. However, some rule applications are truly stateful. For example, the rules accumulated facts with specific attribute values over time and then fired when a certain number was reached. These types of services would require that the workingMemory not be re-created with the receipt of each message, and disposed of after the rules have fired, but have a long-lived working memory that gets added to over time. The current JBossRulesRouter cannot support truly stateful services because it creates a new workingMemory with each message. Truly stateful interactions would require a way to identify the stateful session / working memory that a message is for, and also when to finally dispose of it. -- 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, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-547) Add jbpm support to war deployment

by Kevin Conner (JIRA)

Add jbpm support to war deployment ---------------------------------- Key: JBESB-547 URL: http://jira.jboss.com/jira/browse/JBESB-547 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Add support for jbpm into war deployment -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-548) Remove need for access to the conf directory

by Kevin Conner (JIRA)

Remove need for access to the conf directory -------------------------------------------- Key: JBESB-548 URL: http://jira.jboss.com/jira/browse/JBESB-548 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The current war deployment assumes a single deployment with configuration files obtained from the conf directory The problems with this are - tomcat specific - restricted to a single deployment - write access required to conf directory (will be a problem in secure environments) This should be changed to execute from the war so that multiple deployments can be made and no special security requirements. -- 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, 10 months

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