June 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3574) EPRHelper modifies EPRs when serialising to XML

by Kevin Conner (JIRA)

EPRHelper modifies EPRs when serialising to XML ----------------------------------------------- Key: JBESB-3574 URL: https://issues.jboss.org/browse/JBESB-3574 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 CP2 Reporter: Kevin Conner Assignee: Tom Cunningham The setSpecificEPR initialises a type extension if one is not already present, but this cannot be done safely. Any modifications to an EPR should only be done at the construction point, as it is the creator who is responsible for doing this. I'll attach a diff which configures the type on construction, but we should also consider updating the EPR classes to throw exceptions if modifications are made after the creator has finished with their construction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
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

13 years, 6 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

13 years, 6 months

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

13 years, 6 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

13 years, 6 months

1
2
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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3620) FaultTo does not copy body of message contents

by Ryan LaMothe (JIRA)

FaultTo does not copy body of message contents ---------------------------------------------- Key: JBESB-3620 URL: https://issues.jboss.org/browse/JBESB-3620 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 CP1, 4.9 Environment: Mac OS X, RHEL 5, Windows 7, MySQL 5.x Reporter: Ryan LaMothe We are trying to handle faults in our asynchronous workflows (one way) and are properly setting the faultTo address to a LocalEPR for further processing. When the LocalEPR is called on a fault, the message that we receive contains only the fault and none of the body or any other payload. Unfortunately, that is not enough information to process the message further, alert the caller, etc. The bug appears to be in the org.jboss.soa.esb.listeners.message.errors.Factory class where the message payload is not being copied from the incoming message to the faulty message (see forum thread). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3596) xsd:enumeration value="LOCAL" invmScope service configuration commented out in ESB 4.9 release

by Ryan R. LaMothe (JIRA)

xsd:enumeration value="LOCAL" invmScope service configuration commented out in ESB 4.9 release ---------------------------------------------------------------------------------------------- Key: JBESB-3596 URL: https://issues.jboss.org/browse/JBESB-3596 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.9 Environment: All OS and platforms Reporter: Ryan R. LaMothe Priority: Critical Fix For: 4.9 The jbossesb-1.3.0.xsd file contains the LOCAL invmScope service configuration option but it is commented out.   We need this option to be available in ESB 4.9 as we have a large number of GLOBAL scoped services which really only need to be LOCAL scoped, as we do not want to attach a listener to all of them because listeners are required to use NONE scope. The LOCAL scope should also allow us to avoid adding additional security configurations and work-arounds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3618) Upgrade to jUDDI 3.1.0 snapshots

by Tom Cunningham (JIRA)

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

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3617) Add flag for turning off ivy resolving

by Tom Cunningham (JIRA)

Add flag for turning off ivy resolving -------------------------------------- Key: JBESB-3617 URL: https://issues.jboss.org/browse/JBESB-3617 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 Priority: Minor Fix For: 4.10 Add a flag for turning off the ivy resolving. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2011