June 2010 - 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

15 years, 8 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

15 years, 8 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

15 years, 8 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

15 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3358) Move docs to docbook

by Kevin Conner (JIRA)

Move docs to docbook -------------------- Key: JBESB-3358 URL: https://jira.jboss.org/browse/JBESB-3358 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Kevin Conner Priority: Optional 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, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-3333) Provide support for MRG

by Kevin Conner (JIRA)

Provide support for MRG ----------------------- Key: JBESB-3333 URL: https://jira.jboss.org/browse/JBESB-3333 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.8 Reporter: Kevin Conner Priority: Blocker Fix For: 4.9 Support hornetq as an alternative provider. Need to test integration and selectively include the correct configuration. -- 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, 8 months

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

15 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3335) Integrate MRG with jBPM inflow

by Kevin Conner (JIRA)

Integrate MRG with jBPM inflow ------------------------------ Key: JBESB-3335 URL: https://jira.jboss.org/browse/JBESB-3335 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.8 Reporter: Kevin Conner Priority: Blocker Fix For: 4.9 We currently provide alternative job executor/timers using inflow capabilities and JBoss Messaging. Need to provide hornetq equivalents. -- 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-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-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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2010