February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2355) Fix bpm_orchestration1 readme

by Tom Fennelly (JIRA)

Fix bpm_orchestration1 readme ----------------------------- Key: JBESB-2355 URL: https://jira.jboss.org/jira/browse/JBESB-2355 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Fennelly Fix For: 4.5 Wrong output listing -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2313) Handle wise pooling/concurrency

by Kevin Conner (JIRA)

Handle wise pooling/concurrency ------------------------------- Key: JBESB-2313 URL: https://jira.jboss.org/jira/browse/JBESB-2313 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.5 We need to look at the current wise integration and make sure that we are controlling all aspects that could impact classloading/concurrency. The previous version contains a factory that creates clients using the first client classloader, sharing that with other deployments that may use the same. We need to make sure that each deployment has access to a client using the correct classloader. We also need to take control over the wise configuration as the factory singleton is initialising itself using wise-core.properties obtainable from the first deployment which invokes the factory, ignoring all other properties. As well as making sure that the right properties are used in the right deployment we should also be overriding the temporary directory, if we are within the context of a server, so that the temporary directory is automatically under the server directory and is unique per deployment. The concurrency issues identified in JBESB-2301 should also be checked, as well as checking the current Port access. -- 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

17 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2040) Add barrier-service.xml for embedded console

by Tom Cunningham (JIRA)

Add barrier-service.xml for embedded console -------------------------------------------- Key: JBESB-2040 URL: https://jira.jboss.org/jira/browse/JBESB-2040 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.4 CP1 JBMANCON-422 suggests we still need the barrier service to avoid exceptions on startup. This should be added. -- 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

17 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2260) Remove out of date info from the Services Guide as per SOA QE request?

by Darrin Mison (JIRA)

Remove out of date info from the Services Guide as per SOA QE request? ---------------------------------------------------------------------- Key: JBESB-2260 URL: https://jira.jboss.org/jira/browse/JBESB-2260 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Darrin Mison QE of the SOA 4.3 Services Guide has suggested to remove the following item as it is out of date: Chapter 4 Registry Troubleshooting Scout and jUDDI pitfalls Make sure to put our version of the jaxr-api-1.0.jar, scout-0.7rc2-embedded.jar and the juddi-embedded.jar first. Other versions of these libraries are present in the JBossAS libraries and they are, for the time being, incompatible. This should get resolved in future release of the Application Server. Should this also be updated in the JBoss ESB Services Guide ? -- 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

17 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2340) WSDL serialization not handling normalized entities properly

by Tom Fennelly (JIRA)

WSDL serialization not handling normalized entities properly ------------------------------------------------------------ Key: JBESB-2340 URL: https://jira.jboss.org/jira/browse/JBESB-2340 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.5 -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2334) Allow WSDL publisher to transform WSDL for proxied service

by Kevin Conner (JIRA)

Allow WSDL publisher to transform WSDL for proxied service ---------------------------------------------------------- Key: JBESB-2334 URL: https://jira.jboss.org/jira/browse/JBESB-2334 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.5 WebserviceContractPublisher provides us with the ability to expose a co-located JBossWS webservice through JBR and, with JBESB-1936, we will shortly have the ability to handle remote endpoints. One facility not yet supported is the ability to transform the WSDL from the proxied service, allowing the ESB service to expose a different WSDL. -- 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

17 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2027) Pass WS-A message id/relates to headers into ESB message

by Kevin Conner (JIRA)

Pass WS-A message id/relates to headers into ESB message -------------------------------------------------------- Key: JBESB-2027 URL: https://jira.jboss.org/jira/browse/JBESB-2027 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 -- 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

17 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-2339) Investigate EBWS WS-A test failure under JDK6

by Kevin Conner (JIRA)

Investigate EBWS WS-A test failure under JDK6 --------------------------------------------- Key: JBESB-2339 URL: https://jira.jboss.org/jira/browse/JBESB-2339 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5 The test for the EBWS WS-A WSDL additions appears to be failing under JDK6. I need to investigate to find out why. -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2026) EBWS WS-Addressing is not reflected in the generated WSDL

by Kevin Conner (JIRA)

EBWS WS-Addressing is not reflected in the generated WSDL --------------------------------------------------------- Key: JBESB-2026 URL: https://jira.jboss.org/jira/browse/JBESB-2026 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1 -- 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

17 years, 2 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-2338) Upgrade groovy from 1.0 to 1.5.0

by Kevin Conner (JIRA)

Upgrade groovy from 1.0 to 1.5.0 -------------------------------- Key: JBESB-2338 URL: https://jira.jboss.org/jira/browse/JBESB-2338 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Scripting Affects Versions: 4.4 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.5 This was actually done as part of the recent smooks upgrade, adding this for release notes. -- 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

17 years, 2 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues February 2009