December 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3019) Warning during deployment of webservice_proxy_* quickstarts

by Jiri Pechanec (JIRA)

Warning during deployment of webservice_proxy_* quickstarts ----------------------------------------------------------- Key: JBESB-3019 URL: https://jira.jboss.org/jira/browse/JBESB-3019 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Environment: SOA-P 5 CR4 Reporter: Jiri Pechanec Priority: Minor When a qucikstart with webservice proxy is deployed than log generates warning message 08:01:36,522 WARNING [config] Unable to process deployment descriptor for context '/Quickstart_webservice_proxy_basic' -- 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

14 years, 3 months

5
16
0 / 0

[JBoss JIRA] Created: (JBESB-2444) Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered

by Kevin Conner (JIRA)

Modify JAXRRegistryImpl to coalesce multiple registry object creations when discovered -------------------------------------------------------------------------------------- Key: JBESB-2444 URL: https://jira.jboss.org/jira/browse/JBESB-2444 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 It is possible for the same registry objects to be created concurrently, especially with multiple VMs, leading to certain registry objects being created multiple times when only one occurrence is expected. We need to identify those objects which should be single instances and then have the JAXRRegistryImpl check, then coalesce, any discovered. -- 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

14 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2902) upgrade messaging to latest stable

by Tom Eicher (JIRA)

upgrade messaging to latest stable ---------------------------------- Key: JBESB-2902 URL: https://jira.jboss.org/jira/browse/JBESB-2902 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.6 Reporter: Tom Eicher ESB 4.6 GA still comes with jboss-messaging.jar : > Implementation-Version: 1.4.0.SP3 (build: CVSTag=JBossMessaging_1_4_0_SP3 date=200712131418) Please upgrade to latest stable messaging version. Also: Please include version information in jar name, i.e. /jbossesb-server-4.6/server/default/lib/jboss-messaging-140sp3.jar instead of /jbossesb-server-4.6/server/default/lib/jboss-messaging.jar Thanks, Tom. -- 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

14 years, 3 months

2
12
0 / 0

[JBoss JIRA] Created: (JBESB-2604) Document registry interceptors

by Aaron Pestel (JIRA)

Document registry interceptors ------------------------------ Key: JBESB-2604 URL: https://jira.jboss.org/jira/browse/JBESB-2604 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Environment: SOA-P 4.3 SP1 Reporter: Aaron Pestel Priority: Minor This is a request to document the two known registry interceptors: org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor and org.jboss.internal.soa.esb.services.registry.CachingRegistryInterceptor The InVMRegistryInterceptor is listed in the services guide, section 2.1 and 3.2: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/... In section 2.1, it shows an extract of the registry portion of the jbossesb-properties.xml - which includes InVMRegistryInterceptor, and then goes on to describe each property, but neglects to describe the org.jboss.soa.esb.registry.interceptors property where InVMRegistryInterceptor is set. I am requesting a description in section 2.1 of the org.jboss.soa.esb.registry.interceptors property to include: 1.) format for adding 1 or many interceptors (using ", ") 2.) description of two currently available interceptors (InVMRegistryInterceptor and CachingRegistryInterceptor) 3.) description of when it would make sense or not make sense to use these two interceptors Thanks! -- 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

14 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-2971) Document there are no guarantees that the format on contents of EPR will remain the same

by Taro Yasuma (JIRA)

Document there are no guarantees that the format on contents of EPR will remain the same ---------------------------------------------------------------------------------------- Key: JBESB-2971 URL: https://jira.jboss.org/jira/browse/JBESB-2971 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP3 Reporter: Taro Yasuma See SOA-1589. -- 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

14 years, 3 months

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

14 years, 4 months

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

14 years, 4 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

14 years, 4 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

14 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2783) systinet specific loopback transport

by Kevin Conner (JIRA)

systinet specific loopback transport ------------------------------------ Key: JBESB-2783 URL: https://jira.jboss.org/jira/browse/JBESB-2783 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 We are currently proxying systinet UDDI requests via a mock servlet implementation but we need to investigate implementing a loopback transport as a replacement. It looks like we need to create an implementation of org.idoox.transport.Transport and register this with the TransportRepository. I looked into the JdkClient but this is not what we are after, all it does is use the JDK URLConnection class as the transport. -- 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

14 years, 4 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 December 2009