September 2007 - esb-issues - Jboss List Archives

[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

16 years, 5 months

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

16 years, 5 months

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

16 years, 5 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

16 years, 5 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

16 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-574) Use JAXB instead of Xmlbeans to generate the configuration model.

by Daniel Bevenius (JIRA)

Use JAXB instead of Xmlbeans to generate the configuration model. ----------------------------------------------------------------- Key: JBESB-574 URL: http://jira.jboss.com/jira/browse/JBESB-574 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Optional Use JAXB instead of xmlbeans to generate the configuration model. Kurt suggested this in the following JIRA: http://jira.jboss.com/jira/browse/JBESB-573 -- 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

16 years, 5 months

4
14
0 / 0

[JBoss JIRA] Created: (JBESB-459) Create a message validation cartridge that can be used by Smooks to perform message validation.

by Tom Fennelly (JIRA)

Create a message validation cartridge that can be used by Smooks to perform message validation. ----------------------------------------------------------------------------------------------- Key: JBESB-459 URL: http://jira.jboss.com/jira/browse/JBESB-459 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Mark Little Priority: Optional Fix For: 4.2 Something as simple as cartridge that would allow you target and apply regexp and XPath expressions at parts of a message, generating error/warning reports. I actually used Smooks to prototyped something that's conceptually similar from a validation perspective - analyze a website using Smooks, and generate a report contain possible browser issues with each page (message) e.g. on browser "X" on Mac Os X, this part of the markup may cause usability issues etc (http://milyn.codehaus.org/Smooks+Report+Generator). The cartridge could allow you create "validation" resources that can be targeted at message exchanges (fragments, elements, attributes etc). This might support applying regexp expressions to data values (match, not-match etc - easy enough) as well as using xpath (has-child-element etc easy enough too *I think*). Would obviously get more difficult if you started to add some form of expression language to it - "if attribute matches X and doesn't have child element Y" etc. Might be possible to use JBoss Rules and some form of DSL to wrap the xpath stuff (or even the regex stuff too). -- 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

16 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-732) bpm-based quickstarts should also deploy a process image for jBPM 3.2.1 Admin Console

by Burr Sutter (JIRA)

bpm-based quickstarts should also deploy a process image for jBPM 3.2.1 Admin Console ------------------------------------------------------------------------------------- Key: JBESB-732 URL: http://jira.jboss.com/jira/browse/JBESB-732 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Burr Sutter Priority: Minor Fix For: 4.2 The current jBPM 3.2.1 Admin Console "requires" a process image be deployed with a process definition. Errors are thrown if none is provided. Plus it is more difficult to track the current status of a process instance without the visual representation on the process image. -- 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

16 years, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-692) WARN [BisocketClientInvoker] Message when using bootstrapper

by Burr Sutter (JIRA)

WARN [BisocketClientInvoker] Message when using bootstrapper ------------------------------------------------------------ Key: JBESB-692 URL: http://jira.jboss.com/jira/browse/JBESB-692 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Priority: Minor Fix For: 4.2 The following warning & stack trace show up on the AS console whenever you "Ctrl-C" the bootstrapper. 15:31:36,109 WARN [BisocketClientInvoker] Unable to send ping: shutting down Pi ngTimerTask java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:115) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimer Task.run(BisocketClientInvoker.java:497) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) To recreate: quickstart helloworld 'ant deploy-jms-dests' 'ant run' Ctrl-C The message pops up on the console. Either we need to fix whatever is in the bootstrapper that JBoss Messaging doesn't like (disconnection must be improper) or we need to turn off this warning level. Additional warnings sometimes appear as well: 15:34:53,593 WARN [SimpleConnectionManager] ConnectionManager[c2b246] cannot lo ok up remoting session ID 5c4o22-n5wjzb-f44hz8li-1-f44hz8ze-4 15:34:53,593 WARN [SimpleConnectionManager] A problem has been detected with th e connection to remote client 5c4o22-n5wjzb-f44hz8li-1-f44hz8ze-4. It is possibl e the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed. -- 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

16 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-569) JBoss ESB Template Enhancements

by Tom Cunningham (JIRA)

JBoss ESB Template Enhancements ------------------------------- Key: JBESB-569 URL: http://jira.jboss.com/jira/browse/JBESB-569 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Cunningham Assigned To: Tom Cunningham Here's a list of enhancements that have been suggested: Parameterize the name of the project in the build.xml to match the eclipse project name Parameterize the classnames of the ESB code we generate Add directory jars (jaxr,scout,juddi) To conserve space, pare down jboss-all jar into just the jms classes we need Use InitialContext in SendJMSMessage.java (we have a jndi.properties file) -- 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

16 years, 5 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007