September 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-776) Need a Maven ESB Archetype

by Tom Cunningham (JIRA)

Need a Maven ESB Archetype -------------------------- Key: JBESB-776 URL: http://jira.jboss.com/jira/browse/JBESB-776 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 5.0 We have a maven task which compiles an .esb package. We should also have a maven "archetype" which creates the preferred project layout for Maven. See for details on archetypes http://maven.apache.org/plugins/maven-archetype-plugin/ -- 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, 8 months

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

15 years, 8 months

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

15 years, 8 months

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

15 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2442) Scout creates a new AuthToken for every invocation through BusinessQuery/BusinessLifecycle Managers

by Kevin Conner (JIRA)

Scout creates a new AuthToken for every invocation through BusinessQuery/BusinessLifecycle Managers --------------------------------------------------------------------------------------------------- Key: JBESB-2442 URL: https://jira.jboss.org/jira/browse/JBESB-2442 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The consequence of this is that the jUDDI authentication table keeps growing quickly. -- 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
14
0 / 0

[JBoss JIRA] Created: (JBESB-2110) Move LogicalEPRUnitTest away from files

by Kevin Conner (JIRA)

Move LogicalEPRUnitTest away from files --------------------------------------- Key: JBESB-2110 URL: https://jira.jboss.org/jira/browse/JBESB-2110 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.4 Reporter: Kevin Conner The test relies on the existence of a file for output, leading to an obvious race between creating/reading. We should change this test to pass the messages via an MBean as in the other tests. -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1715) Add support for annotated actions

by Kevin Conner (JIRA)

Add support for annotated actions --------------------------------- Key: JBESB-1715 URL: http://jira.jboss.com/jira/browse/JBESB-1715 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.4 -- 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

4
10
0 / 0

[JBoss JIRA] Created: (JBESB-2862) Add support for XPath based routing using SXC

by Tom Fennelly (JIRA)

Add support for XPath based routing using SXC --------------------------------------------- Key: JBESB-2862 URL: https://jira.jboss.org/jira/browse/JBESB-2862 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Tom Fennelly Fix For: 4.8 Use the existing XPathRouter and RegexRouter impls as a reference. -- 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

1
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2009