May 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3315) Pass jvmargs through build.xml runant macro

by Kevin Conner (JIRA)

Pass jvmargs through build.xml runant macro ------------------------------------------- Key: JBESB-3315 URL: https://jira.jboss.org/jira/browse/JBESB-3315 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.8 -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3314) Change <field .../> to <property .../> in jbpm.cfg.xml

by Kevin Conner (JIRA)

Change <field .../> to <property .../> in jbpm.cfg.xml ------------------------------------------------------ Key: JBESB-3314 URL: https://jira.jboss.org/jira/browse/JBESB-3314 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP4 It has been decided to use <property .../> tags in job executor's configuration in jbpm.cfg.xml instead of <field .../>. -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3102) SOAPClient hardcodes content type to SOAP 1.1 value

by Kevin Conner (JIRA)

SOAPClient hardcodes content type to SOAP 1.1 value --------------------------------------------------- Key: JBESB-3102 URL: https://jira.jboss.org/jira/browse/JBESB-3102 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.8 soap1.2 requries application/soap+xml -- 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

15 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3297) QS tests TransformEDI2XMLGroovyXSLTTest and TransformXML2PojoTest fail when executed in Asian country locale

by Magesh Kumar B (JIRA)

QS tests TransformEDI2XMLGroovyXSLTTest and TransformXML2PojoTest fail when executed in Asian country locale ------------------------------------------------------------------------------------------------------------ Key: JBESB-3297 URL: https://jira.jboss.org/jira/browse/JBESB-3297 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Testing Affects Versions: 4.8 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: 4.9 -- 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

15 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-3295) Make sure we can build and test offline

by Magesh Kumar B (JIRA)

Make sure we can build and test offline --------------------------------------- Key: JBESB-3295 URL: https://jira.jboss.org/jira/browse/JBESB-3295 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.8 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: 4.9 Currently when building without an internet connection, the following test case fails: org.jboss.internal.soa.esb.listeners.war.WebDeploymentArchiveUnitTest -- 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

15 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3296) HttpGateway add support for different connectors

by Kevin Conner (JIRA)

HttpGateway add support for different connectors ------------------------------------------------ Key: JBESB-3296 URL: https://jira.jboss.org/jira/browse/JBESB-3296 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 CP1 Reporter: Kevin Conner Fix For: 4.7 CP2 -- 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

15 years, 11 months

2
5
0 / 0

[JBoss JIRA] Closed: (JBESB-3172) SOAPProxy Service with unreachable proxy URL causes server to hang

by David Ward (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-3172?page=com.atlassian.jira.plu... ] David Ward closed JBESB-3172. ----------------------------- Resolution: Done Tom, thanks again for testing my fix on your Mac. Much appreciated. [trunk]$ svn commit Sending product/rosetta/src/org/jboss/soa/esb/actions/routing/http/AbstractHttpMethodFactory.java Sending product/rosetta/src/org/jboss/soa/esb/actions/routing/http/GETHttpMethodFactory.java Sending product/rosetta/src/org/jboss/soa/esb/actions/routing/http/POSTHttpMethodFactory.java Transmitting file data ... Committed revision 32826. > SOAPProxy Service with unreachable proxy URL causes server to hang > ------------------------------------------------------------------ > > Key: JBESB-3172 > URL: https://jira.jboss.org/jira/browse/JBESB-3172 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Web Services > Affects Versions: 4.7 > Reporter: David Ward > Assignee: David Ward > Fix For: 4.9 > > Attachments: AbstractHttpMethodFactory.java.diff, GETHttpMethodFactory.java.diff, POSTHttpMethodFactory.java.diff, server.log > > > Please read the description and comments in SOA-1928. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-3172) SOAPProxy Service with unreachable proxy URL causes server to hang

by David Ward (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-3172?page=com.atlassian.jira.plu... ] David Ward updated JBESB-3172: ------------------------------ Comment: was deleted > SOAPProxy Service with unreachable proxy URL causes server to hang > ------------------------------------------------------------------ > > Key: JBESB-3172 > URL: https://jira.jboss.org/jira/browse/JBESB-3172 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Web Services > Affects Versions: 4.7 > Reporter: David Ward > Assignee: David Ward > Fix For: 4.9 > > Attachments: AbstractHttpMethodFactory.java.diff, GETHttpMethodFactory.java.diff, POSTHttpMethodFactory.java.diff, server.log > > > Please read the description and comments in SOA-1928. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3233) Turn down the logging on NotifyFTPList

by Tom Fennelly (JIRA)

Turn down the logging on NotifyFTPList -------------------------------------- Key: JBESB-3233 URL: https://jira.jboss.org/jira/browse/JBESB-3233 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Tom Fennelly Priority: Trivial Fix For: 4.9 At the moment, this class is logging debug information as info e.g. "Sending from listFile ...". Turn down to debug. -- 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

15 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3313) Abstraction layer between actions and messages

by David van Balen (JIRA)

Abstraction layer between actions and messages ---------------------------------------------- Key: JBESB-3313 URL: https://jira.jboss.org/jira/browse/JBESB-3313 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: David van Balen I feel that having action developers interact directly with org.jboss.soa.esb.message.Message unnecessarily ties the ESB to a particular message implementation, as well as generating extra work and inconsistency when implementing new actions. It occurred to me that actions could all extend a common base class that abstracts functionality related to manipulating the message, isolating actions from its implementation. For instance, it is currently the action developer's responsibility to place the action's result on the message. While some developers have provided the options of configuring an alternative location from the default for that response, many actions don't seem to provide it. Enforcing that results be placed on the message by calling some kind of "setResult" method,that takes care of checking whether the user has configured an alternate location, would make action implementation more consistent, as well as ensuring that basic functionality like specifying an alternate response location is available across actions. Additionally, things like the exact text of the configuration property would be more likely to remain consistent across actions. Also, abstracting operations related to message attachments and properties would allow how these are implemented to change without breaking a large amount of the codebase. Ideally, action developers should not have access to the message object. -- 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

15 years, 11 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 May 2010