June 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1689) org.jboss.soa.esb.actions.scripting.GroovyActionProcessor doesn't throw an ActionProcessingException if the Process(Message)-method fails

by Morten Damm Jensen (JIRA)

org.jboss.soa.esb.actions.scripting.GroovyActionProcessor doesn't throw an ActionProcessingException if the Process(Message)-method fails ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-1689 URL: http://jira.jboss.com/jira/browse/JBESB-1689 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Morten Damm Jensen The Process(Message)-method in org.jboss.soa.esb.actions.scripting.GroovyActionProcessor is surrounded with a try-catch, and if an Exception is caught is is just logged and then the Message is returned. Instead of returning the Message it should throw an ActionProcessingException! If not, it is impossible for the surrounding environment to take action on this error, and it will assume that the processing was successful. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBESB-1645) SOAPClient process method should guard against ClassCastExceptions on the payload

by Tom Fennelly (JIRA)

SOAPClient process method should guard against ClassCastExceptions on the payload --------------------------------------------------------------------------------- Key: JBESB-1645 URL: http://jira.jboss.com/jira/browse/JBESB-1645 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP2, 4.2.1 CP1 Reporter: Tom Fennelly It's currently just doing a cast to a Map, but not guarding against something else being there. -- 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-1781) Message store class is always logged as null

by Mika Leino (JIRA)

Message store class is always logged as null -------------------------------------------- Key: JBESB-1781 URL: http://jira.jboss.com/jira/browse/JBESB-1781 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.3, 4.2.1 CP1 Environment: Windows Server 2003 Reporter: Mika Leino While debugging a message store action we discovered that the message store class is always logged as null in org.jboss.soa.esb.actions.MessagePersister. In the initialise method the messageStore member's value is logged before it has been initialised leading to confusing log entries. -- 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
3
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-1740) Make InVM Transactional

by Tom Fennelly (JIRA)

Make InVM Transactional ----------------------- Key: JBESB-1740 URL: http://jira.jboss.com/jira/browse/JBESB-1740 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.3 Reporter: Tom Fennelly 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

17 years, 9 months

3
6
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, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-1632) Need a "How to switch Databases" document

by Tom Cunningham (JIRA)

Need a "How to switch Databases" document ----------------------------------------- Key: JBESB-1632 URL: http://jira.jboss.com/jira/browse/JBESB-1632 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 We need a "How to Switch Databases" document for the project. There's a lot of forum posts that ask about how to do this, it'd be nice if we could refer them to a document which explains the steps for each component. -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1686) readme file of helloworld_tx_sql_action needs to be updated

by Jehudi Castro (JIRA)

readme file of helloworld_tx_sql_action needs to be updated ----------------------------------------------------------- Key: JBESB-1686 URL: http://jira.jboss.com/jira/browse/JBESB-1686 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP2 Reporter: Jehudi Castro Priority: Minor As Len says: http://jira.jboss.com/jira/browse/SOA-513#action_12408977 the message (BAD READ ON DATA) and also the RuntimeException is alarming, the readme file should alert about that. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2008