July 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3625) Remove juddiv3.war, grab it from ivy, and remove extraneous files

by Tom Cunningham (JIRA)

Remove juddiv3.war, grab it from ivy, and remove extraneous files ----------------------------------------------------------------- Key: JBESB-3625 URL: https://issues.jboss.org/browse/JBESB-3625 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Remove juddiv3.war, grab it from ivy, and remove extraneous files -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3630) org.jboss.soa.esb.listeners.ScheduleListener does not initiate ActionProcessingPipeline as transacted therefore transaction handling has error.

by Peer Bech Hansen (JIRA)

org.jboss.soa.esb.listeners.ScheduleListener does not initiate ActionProcessingPipeline as transacted therefore transaction handling has error. ----------------------------------------------------------------------------------------------------------------------------------------------- Key: JBESB-3630 URL: https://issues.jboss.org/browse/JBESB-3630 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10, 4.9 Environment: Windows 7, Java version "1.6.0_22", JBossAS 5.1.0GA Reporter: Peer Bech Hansen When org.jboss.soa.esb.listeners.ScheduleListener instantiates and initializes the ActionProcessingPipeline, it never specifies if the ActionProcessingPipeline should be transacted or not. This means that it will never be transacted. This causes that the pipline never throws a RuntimeException back to the ScheduleListener, hence will never mark a transaction to be rolled back. Have a look at line 90 in http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_10/product... ActionProcessingPipeline is instantiated and initialized but the message setTransactional is not called. Have a look at line 692 in http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_10/product... This line will never be executed as the boolean variable 'throwRuntime' is always false for the schedule process. All this leads to the problem that line 123 of ScheduleListener.java is always executed, and the transaction is never rolled back. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3605) Update juddi version to 3.1.0

by Tom Cunningham (JIRA)

Update juddi version to 3.1.0 ----------------------------- Key: JBESB-3605 URL: https://issues.jboss.org/browse/JBESB-3605 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assignee: Tom Cunningham Upgrade juddi version to 3.1.0. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3606) Update scout version to 1.2.3.GA

by Tom Cunningham (JIRA)

Update scout version to 1.2.3.GA -------------------------------- Key: JBESB-3606 URL: https://issues.jboss.org/browse/JBESB-3606 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assignee: Tom Cunningham Update scout version to 1.2.3.GA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3619) Upgrade version number for 4.10 release

by Tom Cunningham (JIRA)

Upgrade version number for 4.10 release --------------------------------------- Key: JBESB-3619 URL: https://issues.jboss.org/browse/JBESB-3619 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 Upgrade version number for the 4.10 release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2760) Verify that the ESB works with the main AS trunk (code base for AS6)

by Daniel Bevenius (JIRA)

Verify that the ESB works with the main AS trunk (code base for AS6) -------------------------------------------------------------------- Key: JBESB-2760 URL: https://jira.jboss.org/jira/browse/JBESB-2760 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 While merging https://jira.jboss.org/jira/browse/JBWS-2619 into the AS main trunk I was not able to deploy the esb. Even without deploying the esb code I get an error upon startup of the as server. I also get an error with our build since conf/jboss-log4.xml does not exist in the server created by the as trunk. This file is replaced by build.xml in product/install/embedded-console. This might be temporary as the trunk code base is a moving target but we should still make sure when they get closer to a release date to make sure that we are not depending on something that is going to be removed. I'm not sure that this is required for our 4.7 release, as this depends on the release schedule for AS6. But I'm setting the version to 4.7 so that a decision should be made about this. -- 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

12 years, 10 months

5
19
0 / 0

[JBoss JIRA] Created: (JBESB-3621) Upgrade docs for 4.10 release

by Tom Cunningham (JIRA)

Upgrade docs for 4.10 release ----------------------------- Key: JBESB-3621 URL: https://issues.jboss.org/browse/JBESB-3621 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 Upgrade documentation for the 4.10 release -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3623) Upgrade Drools to 5.2.0.Final

by Tom Cunningham (JIRA)

Upgrade Drools to 5.2.0.Final ----------------------------- Key: JBESB-3623 URL: https://issues.jboss.org/browse/JBESB-3623 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 Upgrade Drools to 5.2.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3624) Change deprecated jboss repository URLs

by Tom Cunningham (JIRA)

Change deprecated jboss repository URLs --------------------------------------- Key: JBESB-3624 URL: https://issues.jboss.org/browse/JBESB-3624 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 Change deprecated JBoss repository URLs to new nexus URLs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2011