January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-498) Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware.

by Tom Fennelly (JIRA)

Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware. --------------------------------------------------------------------------------------------------------- Key: JBESB-498 URL: http://jira.jboss.com/jira/browse/JBESB-498 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 This will also mean adding query capability against this. This requirement could be generalised to simply allow registrations to be decorated with attributes, and have these same attributes returned in the lookups. -- 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

17 years, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-1470) Webservice QS CI tests need debugging

by Tom Cunningham (JIRA)

Webservice QS CI tests need debugging ------------------------------------- Key: JBESB-1470 URL: http://jira.jboss.com/jira/browse/JBESB-1470 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 The webservice* QS CI tests are excluded currently because they do not find a record after their wait period when run within the test harness. When run individually under the "ant internal-one-test" target, these tests all work fine. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-522) Controlled shutdown

by Kevin Conner (JIRA)

Controlled shutdown ------------------- Key: JBESB-522 URL: http://jira.jboss.com/jira/browse/JBESB-522 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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

17 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-962) WS-CDL as the overall design and development methodology

by Mark Little (JIRA)

WS-CDL as the overall design and development methodology -------------------------------------------------------- Key: JBESB-962 URL: http://jira.jboss.com/jira/browse/JBESB-962 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow, Rosetta Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 -- 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

17 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1306) Version class for all jars produced.

by Daniel Bevenius (JIRA)

Version class for all jars produced. ------------------------------------ Key: JBESB-1306 URL: http://jira.jboss.com/jira/browse/JBESB-1306 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Priority: Trivial One can get the version of jbossesb-rosetta.jar by typing: (the actual information is configurable in build.xml) >java -jar build/jbossesb/lib/jbossesb-rosetta.jar #JBoss ESB Product Information #Fri Nov 02 10:32:08 CET 2007 Version=4.2.1GA This Jira should add the same functionality to the other jars created by the build. -- 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

17 years, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1426) CBR XPathDSL should allow namespace aware documents

by Vinicius Carvalho (JIRA)

CBR XPathDSL should allow namespace aware documents --------------------------------------------------- Key: JBESB-1426 URL: http://jira.jboss.com/jira/browse/JBESB-1426 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 Reporter: Vinicius Carvalho Priority: Optional Current version of DSLHelper, does not allow one to use namespace documents to be routed. For instance, the document <acme:bomb xmlns:acme="http://acme.com/schemas"> <acme:model></acme:model> </acme:bomb> does not work with the xpath expression : "//acme:model" since the xpath is not namespace-aware. The use of a namespace should allow this, the action should support it, for instance: <action name="ContentBasedRouter" class="org.jboss.soa.esb.actions.ContentBasedRouter"> <property name="namespaces"> <namespace prefix="acme" uri="http://acme.com/schemas"/> <namespace prefix="foo" uri="http://bar.com/schemas"/> </property> </action> On the configuration of the action (sorry still trying to figure where to put this :( ) the following namespace could be used: package com.synos.csm.eai.xml; import javax.xml.XMLConstants; import javax.xml.namespace.NamespaceContext; import java.util.Iterator; import java.util.Map; import java.util.HashMap; import java.util.Set; import java.util.ArrayList; import java.util.List; public class CustomNamespaceContext implements NamespaceContext { private Map map; public CustomNamespaceContext() { map = new HashMap(); map.put(XMLConstants.XML_NS_PREFIX, XMLConstants.XML_NS_URI); map.put(XMLConstants.XMLNS_ATTRIBUTE, XMLConstants.XMLNS_ATTRIBUTE_NS_URI); } public void addNamespace(String prefix, String namespaceURI) { map.put(prefix, namespaceURI); } public String getNamespaceURI(String prefix) { return (String) map.get(prefix); } public String getPrefix(String namespaceURI) { Set keys = map.keySet(); for (Iterator iterator = keys.iterator(); iterator.hasNext();) { String prefix = (String) iterator.next(); String uri = (String) map.get(prefix); if (uri.equals(namespaceURI)) return prefix; } return null; } public Iterator getPrefixes(String namespaceURI) { List prefixes = new ArrayList(); Set keys = map.keySet(); for (Iterator iterator = keys.iterator(); iterator.hasNext();) { String prefix = (String) iterator.next(); String uri = (String) map.get(prefix); if (uri.equals(namespaceURI)) prefixes.add(prefix); } return prefixes.iterator(); } } now, inside the DSLHelper, set the namespace aware xpath: //check if user has set the namespace property if(namespaceAware) xpath.setNamespaceContext(customNamespaceForThisAction); I had to override the DSLHelper in my project, I guess that this approach should help a lot -- 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

17 years, 10 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1343) Integrate JBossWS test suite with the ESB

by Heiko Braun (JIRA)

Integrate JBossWS test suite with the ESB ----------------------------------------- Key: JBESB-1343 URL: http://jira.jboss.com/jira/browse/JBESB-1343 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Heiko Braun Assigned To: Heiko Braun Fix For: 4.3 We need to execute the jbossws smoke tests (jax-ws baseline) against the ESB. -- 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

17 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-1504) CBR using rules has poor performance

by Martin Vecera (JIRA)

CBR using rules has poor performance ------------------------------------ Key: JBESB-1504 URL: http://jira.jboss.com/jira/browse/JBESB-1504 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2.1 Environment: SOA-P 4.2.0.beta1 Reporter: Martin Vecera We have a simple performance that uses ContentBasedRouter to route XML messages: <action class="org.jboss.soa.esb.actions.ContentBasedRouter" name="ContentBasedRouter"> <property name="ruleSet" value="MyESBRules-XPath.drl"/> <property name="ruleLanguage" value="XPathLanguage.dsl"/> <property name="ruleReload" value="true"/> <property name="destinations"> <route-to destination-name="regular1" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular2" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular3" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular4" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular5" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular6" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular7" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular8" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular9" service-category="wiretapCategory1" service-name="regularService"/> <route-to destination-name="regular0" service-category="wiretapCategory1" service-name="catchService"/> </property> </action> I have created a rule set of 100 rules. Like this: package com.jboss.soa.esb.routing.cbr import org.jboss.soa.esb.message.Message; import org.jboss.soa.esb.message.format.MessageType; expander XPathLanguage.dsl global java.util.List destinations; rule "ProductId1" salience 100 when xpathEquals "/Order/OrderLines/OrderLine/Product/@productId", "1" then Destination : "regular1"; end ... rule "ProductId299" salience 100 when xpathEquals "/Order/OrderLines/OrderLine/Product/@productId", "299" then Destination : "regular0"; end rule "Default rule" salience 1 when then Destination : "regular0"; end See https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/performan... for the whole file. The performance is very poor (see SOA-240 for reports). Only a tens of messages per second. What's the problem here? Is the Rules engine really so slow? Or is it parsing the file every time a message arrives? -- 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

17 years, 10 months

4
24
0 / 0

[JBoss JIRA] Created: (JBESB-1445) Message Store does not participate in JTA transaction

by Jiri Pechanec (JIRA)

Message Store does not participate in JTA transaction ----------------------------------------------------- Key: JBESB-1445 URL: http://jira.jboss.com/jira/browse/JBESB-1445 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Mark Little Fix For: 4.2.1 CP1 Service uses JCA/JMS listener and stores message to message store. If the transaction is rolled back then the messages will reatin in message store as it does not participate in global JTA transaction. -- 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

17 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1153) File Gateway: Consume only a single file at a time

by Burr Sutter (JIRA)

File Gateway: Consume only a single file at a time -------------------------------------------------- Key: JBESB-1153 URL: http://jira.jboss.com/jira/browse/JBESB-1153 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.3 The current File gateway consumes files at a rate faster than the internal/native listener (typically JMS-based) and its associated action chain. This request is for a configuration property that causes the rate of consumption of the file gateway to match the underlying internal/native listener. Basically a file would not be pulled from disk until it has completely passed through the action chain. Here are some notes related to this use case: I have 1000+ files which are very huge in size and when all the files are kept in the folder they are read at same time and placed in configured JMS Queue. - When all the files are placed in Queue there is a chance that the size of messages in Queue may exceed and it may not accept new messages? Or - Sometimes the case may be like the input folder is monitored by one person and the message processing is monitored by other person. In this case when all the files are read at once it gives a wrong assumption that all files are processed but where as due to some application failure the messages may still be in queue. Or - Its always a good option to be able to see how many messages are still in process in the folder rather than browsing the JMS queue and looking for Queue depth. In this case if you look at Queue depth sometimes it may be give you wrong count of messages as there is a chance that some other application also put message some messages into the same queue, when Queue is configured for application sharing. Or - If you want to replace a single file out of 1000+ files in the input folder while in middle of processing the files, it will be easy if the files are read one at a time rather going and deleting the messages from JMS queue after they are read at once and placed in Queue. -- 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

17 years, 10 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008