July 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3387) Turn down deployment logging on CamelGateway

by Tom Fennelly (JIRA)

Turn down deployment logging on CamelGateway -------------------------------------------- Key: JBESB-3387 URL: https://jira.jboss.org/browse/JBESB-3387 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 CamelGateway is outputting the following info log (should be debug)... 19:05:19,690 INFO [CamelGateway] adding routes [ <routes xmlns="http://camel.apache.org/schema/spring"> <route> <from uri="file:///Users/tfennelly/jboss/esb/trunk/product/samples/quickstarts/camel_helloworld/build/input1?delete=true"/> <to uri="jbossesb://service?category=camel_helloworld&name=service1&async=false&timeout=30000"/> </route> <route> <from uri="file:///Users/tfennelly/jboss/esb/trunk/product/samples/quickstarts/camel_helloworld/build/input2?delete=true"/> <to uri="jbossesb://service?category=camel_helloworld&name=service1&async=false&timeout=30000"/> </route> </routes> ] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-2882) Add support for fireUntilHalt to BusinessRulesProcessor

by Jeff DeLong (JIRA)

Add support for fireUntilHalt to BusinessRulesProcessor ------------------------------------------------------- Key: JBESB-2882 URL: https://jira.jboss.org/jira/browse/JBESB-2882 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Jeff DeLong To better support CEP, an ESB Rule Service should be able to create the KnowledgeBase, StatefulKnowledgeSession, etc, and then execute fireUntilHalt. This will cause the thread to block, and the rules engine will continue to process (in a separate thread). Either the same ESB Service, or different service with access to the StatefulKnowledgeSession, can then receive messages / events and insert them into the StatefulKnowledgeSession. FireUntil Halt provides two important benefits to a CEP application. First it provides more timely rules firing. Even more important, it support the case where the absence of incoming events should cause rules to fire. -- 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

15 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-3393) StackOverflowError in Drools DelegatingSystemEventListener

by David Ward (JIRA)

StackOverflowError in Drools DelegatingSystemEventListener ---------------------------------------------------------- Key: JBESB-3393 URL: https://jira.jboss.org/browse/JBESB-3393 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing, Deployment Affects Versions: 4.9 Reporter: David Ward Assignee: David Ward Fix For: 4.9 A stack overflow error can be encountered in cases where the drools default SystemEventListener is a DelegatingSystemEventListener. We need to detect this case and handle it appropriately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3392) Upgrade Camel from 2.3.0 to 2.4.0

by David Ward (JIRA)

Upgrade Camel from 2.3.0 to 2.4.0 --------------------------------- Key: JBESB-3392 URL: https://jira.jboss.org/browse/JBESB-3392 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.9 Reporter: David Ward Assignee: David Ward Fix For: 4.9 Camel 2.4.0 has 182 issues resolved since 2.3.0. Let's make sure we get those fixes before we release ESB 4.9 with the new CamelGateway. http://camel.apache.org/camel-240-release.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3390) Update Spring dependency to version 2.5.6.SEC01 - version mismatches cause problems with RiftSaw

by Aleksander Adamowski (JIRA)

Update Spring dependency to version 2.5.6.SEC01 - version mismatches cause problems with RiftSaw ------------------------------------------------------------------------------------------------ Key: JBESB-3390 URL: https://jira.jboss.org/browse/JBESB-3390 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Aleksander Adamowski Currently, JBossESB deploys with spring jars for Spring 2.5.5. At the same time, the latest release of RiftSaw BPEL engine deploys with spring-aspects-2.5.6.SEC01.jar and spring-2.5.6.SEC01.jar. The version mismatch between ESB and RiftSaw causes problems when making use of some features of Spring Framework in Riftsaw's CXF web service endpoint configuration descriptors. E.g. if one tries to create a bean for accessing EJBs to be used by CXF interceptors: <bean id="ejbProxyBean" class="org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean"> <property name="jndiName" value="SomeSessionEJB"/> <property name="businessInterface" value="SomeSessionEJBInterface"/> </bean> The result is an exception in the logs: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ejbProxyBean' .... .... Caused by: java.lang.NoSuchMethodError: org.springframework.util.ReflectionUtils.isEqualsMethod(Ljava/lang/reflect/Method;)Z at org.springframework.aop.support.AopUtils.isEqualsMethod(AopUtils.java:118) at org.springframework.aop.framework.JdkDynamicAopProxy.findDefinedEqualsAndHashCodeMethods(JdkDynamicAopProxy.java:131) at org.springframework.aop.framework.JdkDynamicAopProxy.getProxy(JdkDynamicAopProxy.java:116) at org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:110) at org.springframework.ejb.access.LocalStatelessSessionProxyFactoryBean.afterPropertiesSet(LocalStatelessSessionProxyFactoryBean.java:89) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1368) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1334) That's because there was no isEqualsMethod() in Spring 2.5.5's version of ReflectionUtils. The latest release of Spring is 2.5.6.SEC01, and JBoss ESB should update to that, especially considering that it's a security fix release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-2830) Add Stream Mode support to BusinessRulesProcessor

by Jeff DeLong (JIRA)

Add Stream Mode support to BusinessRulesProcessor ------------------------------------------------- Key: JBESB-2830 URL: https://jira.jboss.org/jira/browse/JBESB-2830 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jeff DeLong The BusinessRulesProcessor should support configuration for "StreamMode" with StatelessKnowledgeSessions. Most CEP applications will require StreamMode to enable sliding window support, garbage collection of expired facts, etc. This is really important (a necessity), and is turned on through the API. This would require configuration such as <action class="org.jboss.soa.esb.actions.BusinessRulesProcessor" name="OrderCountHistory"> <property name="ruleSet" value="OrderCount.drl"/> <property name="ruleReload" value="true"/> <property name="stateful" value="true"/> <property name="vventProcessingOption " value="STREAM"/> The code to use this would be something like: kconfig = KnowledgeBaseFactory.newKnowledgeBaseConfiguration(); kconfig.setOption( EventProcessingOption.STREAM ); kbase = readKnowledgeBase(kconfig); sconfig = KnowledgeBaseFactory.newKnowledgeSessionConfiguration(); sconfig.setOption( ClockTypeOption.get( ClockType.REALTIME_CLOCK.getId() ) ); ksession = kbase.newStatefulKnowledgeSession(sconfig, null); -- 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

15 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2831) Add Exit Point support to BusinessRulesProcessor

by Jeff DeLong (JIRA)

Add Exit Point support to BusinessRulesProcessor ------------------------------------------------ Key: JBESB-2831 URL: https://jira.jboss.org/jira/browse/JBESB-2831 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jeff DeLong ExitPoint support should be provided with BusinessRulesProcess. This would allow one or more ExitPoints to be declared in the ESB service configuration. Basically exit point support would take the object inserted into the exit point from the rule, create a new ESBMessage, copy the object into the ESB Message based on the exit point configuration, and send the ESB message to a configured "destination" (similar to a router configuration). This would require configuration such as <action class="org.jboss.soa.esb.actions.BusinessRulesProcessor" name="OrderCountHistory"> <property name="ruleSet" value="OrderCount.drl"/> <property name="ruleReload" value="true"/> <property name="stateful" value="true"/> <property name="object-paths"> <object-path entry-point="OrderEntryPoint" esb="body.TheOrderHeader"/> </property> <property name="exitPoint value="OrderExitPoint" <route-to destination-name="x" service-category="y" service-name="z"/> <need to either use set-payload-location or object mapper to map location of added data in new message> </property> </action> The configuration of multiple exit points should be allowed. A class would then need to be added that implemented the ExitPointInterface and was instantiated and configured from the BusinessRulesProcessor such as: public class RulesExitPointServiceInvoker implements ExitPoint { // constructor with configuration details // service category, service name, and object mapping or set-payload-location details // required method public void insert(Object object) { try { ServiceInvoker invoker = new ServiceInvoker(service-category, service-name); Message requestMessage; requestMessage = MessageFactory.getInstance().getMessage(MessageType.JBOSS_XML); // add payload stuff /object mapping requestMessage.getBody().add(object); invoker.deliverAsync(requestMessage); } catch (MessageDeliverException mde) { System.out.println("Eating this Exception: " + mde); } } } where the BRP code looked like: RulesExitPointServiceInvokerr exit = new RulesExitPointServiceInvoker(); KnowledgeRuntime kruntime = (KnowledgeRuntime) ksession.getEnvironment(); kruntime.registerExitPoint("exit-point", exit); -- 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

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2883) Support Drools audit log in BusinessRulesProcessor

by Jeff DeLong (JIRA)

Support Drools audit log in BusinessRulesProcessor -------------------------------------------------- Key: JBESB-2883 URL: https://jira.jboss.org/jira/browse/JBESB-2883 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Jeff DeLong It would be nice if the BusinessRulesProcessor allowed for configuration of a log file for audit logging. This audit log can then be read by the JBTools Drools Audit viewer. Which is very convenient for debugging. The API looks like: logger = KnowledgeRuntimeLoggerFactory.newThreadedFileLogger(ksession, "log/audit", 500); So the configuration requires the path to the log file (relative path will be from the bin directory and the user must create the log directory in bin) as well as the time interval after which the log will be written, e.g. 500 milliseconds. -- 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

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3360) Upgrade Drools to latest 5.1 Milestone Release

by David Ward (JIRA)

Upgrade Drools to latest 5.1 Milestone Release ---------------------------------------------- Key: JBESB-3360 URL: https://jira.jboss.org/browse/JBESB-3360 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration, Content Based Routing, Documentation, Examples Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Fix For: 4.9 ESB 4.9 is the project release feeding SOA-P 5.1, which will use Drools 5.1. We need to upgrade ESB from Drools 5.0.1 to the latest 5.1.0 Milestone Release. It is currently at M2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3388) Remove hotnetq-jms.xml config from camel_helloworld quickstart

by Tom Fennelly (JIRA)

Remove hotnetq-jms.xml config from camel_helloworld quickstart -------------------------------------------------------------- Key: JBESB-3388 URL: https://jira.jboss.org/browse/JBESB-3388 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release, Examples Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2010