July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-570) Configuration of JBoss AS installation directory in deployment.properties for ESB trailblazers fails if a relative path is used or the path name contains spaces

by Pete Bennett (JIRA)

Configuration of JBoss AS installation directory in deployment.properties for ESB trailblazers fails if a relative path is used or the path name contains spaces ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-570 URL: http://jira.jboss.com/jira/browse/JBESB-570 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Environment: Fedora Core 6 J2SE 5 Ant 1.6.5 Reporter: Pete Bennett Assigned To: Mark Little Priority: Minor In the Quickstart guide and the Trailblazers, one needs to configure the deployment.properties file to point at an installation of JBoss AS with EJB3 enabled. If the path specified includes a space then things will seem to work, but when you try to start up the JBoss AS server for the Quickstart example, you get an error in the JBoss AS console Window when the ESB service tries to parse this pass as follows: 11:14:06,973 INFO [DatabaseInitializer] Initializing java:/juddiDB from listed sql files 11:14:07,166 INFO [JuddiRMIService] starting juddi RMI service 11:14:07,171 WARN [ServiceController] Problem starting service jboss.esb:service=JuddiRMI java.net.URISyntaxException: Illegal character in path at index 31: file:/home/pbennett/JBoss/JBoss ESB/4.2MR2/jbossesb-server/server/default/deploy/jbossesb.sar/esb.juddi.properties at java.net.URI$Parser.fail(URI.java:2816) at java.net.URI$Parser.checkChars(URI.java:2989) at java.net.URI$Parser.parseHierarchical(URI.java:3073) at java.net.URI$Parser.parse(URI.java:3021) at java.net.URI.<init>(URI.java:578) at org.jboss.internal.soa.esb.dependencies.JuddiRMIService.startService(JuddiRMIService.java:63) ... If you use a relative path rather than an absolute path, then the Quickstart example works when run from the original directory but the other Trailblazer examples fail to find the correct directory as they look relative to themselves rather than relative to the root. -- 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

15 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-467) Reducing registry lookup overhead

by Mark Little (JIRA)

Reducing registry lookup overhead --------------------------------- Key: JBESB-467 URL: http://jira.jboss.com/jira/browse/JBESB-467 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2, 5.0 >From our previous discussion on reducing registry lookup overhead (currently lookup per message send): There are a number of solutions to this and we should try to support them all eventually: (i) EPR lifetime: service deployers can register a lifetime associated with the EPR in the registry and when something reads the EPR it also receives information on how long the EPR will remain valid for. After that time elapses, clients must go back to the registry to get a new copy. (ii) building on (i), EPRs can be marked as persistent - they never change so one lookup will always be enough. (iii) interactions with services are scoped by sessions and the EPR is assumed to remain valid for the duration of the session. The service can be marked as useable within such a session. (iv) EPRs are looked up once per client lifecycle and only rebound if the service fails. If you recall from the original ESB architecture document, service migration is something that is on the roadmap (5.0) and if a service moves it can leave a forwarding address (EPR) and the architecture allows messages to be redirected and eventually short-cut, i.e., the client EPR is updated with the new EPR transparently as a result of receiving a response from a different endpoint. (iii) and (iv) are really for the 5.0 architecture. However, it should be possible to add something along (i) and (ii) for 4.0. What do you think? -- 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

15 years, 9 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-498) Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware.

by Tom Fennelly (JIRA)

Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware. --------------------------------------------------------------------------------------------------------- Key: JBESB-498 URL: http://jira.jboss.com/jira/browse/JBESB-498 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 This will also mean adding query capability against this. This requirement could be generalised to simply allow registrations to be decorated with attributes, and have these same attributes returned in the lookups. -- 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

15 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-522) Controlled shutdown

by Kevin Conner (JIRA)

Controlled shutdown ------------------- Key: JBESB-522 URL: http://jira.jboss.com/jira/browse/JBESB-522 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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

15 years, 9 months

2
2
0 / 0

[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

15 years, 10 months

3
5
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

15 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

15 years, 10 months

4
8
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

15 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

15 years, 10 months

4
6
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

15 years, 10 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007