August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-839) The tests in services don't obey the same run rules as elsewhere

by Mark Little (JIRA)

The tests in services don't obey the same run rules as elsewhere ---------------------------------------------------------------- Key: JBESB-839 URL: http://jira.jboss.com/jira/browse/JBESB-839 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam We agreed early on that tests would be named UnitTest, FuncTest or IntegrationTest and we'd have rules to cover the running of them. Basic rule would just run Func and Unit tests. Integration testing would run them all. The services test rule just runs everything with a Test name. This should be brought in line with the rest of 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-838) MessageStore test should be renamed to either MessageStoreUnitTest, MessageStoreFuncTest or MessageStoreIntegrationTest

by Mark Little (JIRA)

MessageStore test should be renamed to either MessageStoreUnitTest, MessageStoreFuncTest or MessageStoreIntegrationTest ----------------------------------------------------------------------------------------------------------------------- Key: JBESB-838 URL: http://jira.jboss.com/jira/browse/JBESB-838 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial -- 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

18 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-840) FTP Quickstart not deploying properly because it can't pick up the ftp config from quickstart.properties

by Tom Fennelly (JIRA)

FTP Quickstart not deploying properly because it can't pick up the ftp config from quickstart.properties -------------------------------------------------------------------------------------------------------- Key: JBESB-840 URL: http://jira.jboss.com/jira/browse/JBESB-840 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Kevin Conner Fix For: 4.2 Tom Fennelly wrote: > > Hi there. > > > > In order to get the FTP helloworld quickstart to deploy, I had to > > locally modify the following in base-build.xml... > > > > <target name="assert-ftp-config"> > > <condition property="quickstart.ftp.config"> > > <and> > > <isset property="jbossesb.ftp.hostname"/> > > <isset property="jbossesb.ftp.username"/> > > <isset property="jbossesb.ftp.password"/> > > <isset property="jbossesb.ftp.directory"/> > > </and> > > </condition> > > <fail unless="quickstart.ftp.config" message="Please configure > > ftp properties in quickstart.properties"/> > > </target> > > .. to... > > <target name="assert-ftp-config"> > > <condition property="quickstart.ftp.config"> > > <and> > > <isset property="quickstart.jbossesb.ftp.hostname"/> > > <isset property="quickstart.jbossesb.ftp.username"/> > > <isset property="quickstart.jbossesb.ftp.password"/> > > <isset property="quickstart.jbossesb.ftp.directory"/> > > </and> > > </condition> > > <fail unless="quickstart.ftp.config" message="Please configure > > ftp properties in quickstart.properties"/> > > </target> > > > > Anyone any ideas? Kev? Yes, it has been broken. Create a JIRA and assign it to me, I'll fix it. It is related to embedding the QSes into 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

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-829) Add the original server-side exception to the returned Fault

by Mark Little (JIRA)

Add the original server-side exception to the returned Fault ------------------------------------------------------------ Key: JBESB-829 URL: http://jira.jboss.com/jira/browse/JBESB-829 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-795) Investigate issue with webservice_consumer2 quickstart

by Tom Fennelly (JIRA)

Investigate issue with webservice_consumer2 quickstart ------------------------------------------------------ Key: JBESB-795 URL: http://jira.jboss.com/jira/browse/JBESB-795 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 Just thought it'd be better to log this as a JIRA task so as to keep track of sidetracking issues like this. -- 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

18 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-831) Add an application ability to remove messages from the DLQ

by Mark Little (JIRA)

Add an application ability to remove messages from the DLQ ---------------------------------------------------------- Key: JBESB-831 URL: http://jira.jboss.com/jira/browse/JBESB-831 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 5.0 It would be useful for certain applications to be able to remove messages from the DLQ even if they were automatically added by the ESB. For example, suppose that the ESB adds a message to the DLQ because the service was down. The application knows this and most of the time it's fine. However, in some situations (specifically in the async case) it may use the DLQ as a backup to it's own application level retries, e.g., trying to do something else to compensate for the failure to deliver. If this "something else" fails, then the DLQ redelivery is good. If it succeeds, it may not be necessary (or wise) to let the redelivery from the DLQ go ahead. -- 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

18 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-709) jbpm CommandInterpreter action fails silently within doTheJob

by Kevin Conner (JIRA)

jbpm CommandInterpreter action fails silently within doTheJob ------------------------------------------------------------- Key: JBESB-709 URL: http://jira.jboss.com/jira/browse/JBESB-709 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Kevin Conner Assigned To: Mark Little The doTheJob method of CommandInterpreter wraps all exception within the body of the current message. These values appear to be ignored as errors do not terminate processing. -- 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

18 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-830) DLQ is used in ServiceInvoker.deliverSync

by Mark Little (JIRA)

DLQ is used in ServiceInvoker.deliverSync ----------------------------------------- Key: JBESB-830 URL: http://jira.jboss.com/jira/browse/JBESB-830 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.2 I thought it would only kick-in automatically in the case of deliveryAsync. For synchronous we should leave it up to the sender to invoke the DLQ when/if a sync failure error occurs. If it's automatic then it may actually conflict with the application's attempt to do something else at that level. For example, sending a synchronous "debit my current account" message to BankA fails, so the application then decides to send a "debit my savings account" message to BankB, which succeeds. However, later on because we put the first "debit my current account" request into the DLQ and redelivery kicks in, it eventually gets delivered and both accounts are subsequently debited. That sort of inconsistency shouldn't happen in the synchronous case. It can't help but happen in the async case unless the application programmer does something at the application level, and in which case it's out of our domain anyway. -- 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

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-828) product/services/jbossesb/src/test has esb.esb in package hierarchy

by Mark Little (JIRA)

product/services/jbossesb/src/test has esb.esb in package hierarchy ------------------------------------------------------------------- Key: JBESB-828 URL: http://jira.jboss.com/jira/browse/JBESB-828 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam Priority: Trivial Fix For: 4.2.1 org.jboss.soa.esb.esb.persistence should be org.jboss.soa.esb.persistence, right? -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-824) Product build bug: leaves out the "scripts" folder when producing jbossesb-rosetta.jar

by Burr Sutter (JIRA)

Product build bug: leaves out the "scripts" folder when producing jbossesb-rosetta.jar -------------------------------------------------------------------------------------- Key: JBESB-824 URL: http://jira.jboss.com/jira/browse/JBESB-824 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Reporter: Burr Sutter Assigned To: Mark Little Priority: Critical Fix For: 4.2 The current jbossesb-rosetta.jar file "drops" the org\jboss\soa\esb\listeners\gateway\scripts folder from the final distro. The Groovy gateway uses this script: rosetta\src\org\jboss\soa\esb\listeners\gateway\scripts\MessageInjectionConsole.groovy This script should be available to this jboss-esb.xml when using the Groovy "gateway" <service category="MyGroovy" name="ACustomService" description="EPR Description" > <listeners> <groovy-listener name="groovy-client" script="MessageInjectionConsole.groovy" is-gateway="true" /> <jms-listener name="ESBListener" busidref="quickstartEsbChannel" maxThreads="1"/> </listeners> <actions> <action name="first" class="org.jboss.soa.esb.samples.quickstart.groovygateway.MyBasicAction" process="displayMessage" > <property name="exceptionMethod" value="exceptionHandler" /> </action> </actions> </service> My workaround for now is to copy that .groovy file into my .esb archive since it is missing from the base product's jars. -- 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

18 years, 8 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007