February 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1553) SOAPClient action remappes objects with null strings to empty strings

by Jiri Pechanec (JIRA)

SOAPClient action remappes objects with null strings to empty strings --------------------------------------------------------------------- Key: JBESB-1553 URL: http://jira.jboss.com/jira/browse/JBESB-1553 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP2 Use webservice_consumer2 quickstart and use the attached files - contains enhanced equals and toString defintions. Make sure that option1 is used. The object with following contents is sent to processing to ivoke web service id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = null But in the web service processing method the contents is id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = The difference is in shipTo property which was set tu null on the input but comes to web service as empty string. -- 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

15 years, 10 months

5
21
0 / 0

[JBoss JIRA] Created: (JBESB-2270) Provide an alternative for bean configured action

by Kevin Conner (JIRA)

Provide an alternative for bean configured action ------------------------------------------------- Key: JBESB-2270 URL: https://jira.jboss.org/jira/browse/JBESB-2270 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner Fix For: 4.x The bean configured action code has a number of deficiencies which include the following - instantiation of the action per message - no support for standard callbacks (including lifecycles) We should create an alternative which creates a single instance of the action, configures properties through reflection and also supports the standard callback methods. -- 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-1171) Remove usages org.jboss.soa.esb.listeners.message.MockMessageComposer and replace with BasicMessageComposer

by Tom Fennelly (JIRA)

Remove usages org.jboss.soa.esb.listeners.message.MockMessageComposer and replace with BasicMessageComposer ----------------------------------------------------------------------------------------------------------- Key: JBESB-1171 URL: http://jira.jboss.com/jira/browse/JBESB-1171 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 IR1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 Not doing anything extra -- 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

15 years, 11 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-800) Provide in the documentation the links of the existing wiki pages for the quickstart samples.

by angel asencio (JIRA)

Provide in the documentation the links of the existing wiki pages for the quickstart samples. --------------------------------------------------------------------------------------------- Key: JBESB-800 URL: http://jira.jboss.com/jira/browse/JBESB-800 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor To list any existing wiki quickstart sample link under the corresponding quickstart sample listed in the GettingStarted Guide and the readme.txt of that quickstart sample. For examples: There exist a wiki for the Hello World quickstart: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossESBHelloworld This should be listed under the listing of helloworld in the Getting Started Guide and in the readme.txt of the helloworld quickstart sample. -- 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

15 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-801) Wiki pages should be create for all JBoss ESB Quickstarts.

by angel asencio (JIRA)

Wiki pages should be create for all JBoss ESB Quickstarts. ---------------------------------------------------------- Key: JBESB-801 URL: http://jira.jboss.com/jira/browse/JBESB-801 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: angel asencio Assigned To: Mark Little Priority: Minor Wiiki pages should be provided like the ones created for the quickstart samples helloworld and simple_cbr that ease the understanding of these concepts. In addition it can provide navigation links to dependent concepts or concepts that the quickstart sample depends on. -- 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

15 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1912) There are two HttpRouter actions in codebase

by Jiri Pechanec (JIRA)

There are two HttpRouter actions in codebase -------------------------------------------- Key: JBESB-1912 URL: https://jira.jboss.org/jira/browse/JBESB-1912 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 There is org.jboss.soa.esb.actions.routing.HttpRouter action. This action does not support standard router features and should be removed. -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2447) Add quickstart for HttpGateway

by Jim Ma (JIRA)

Add quickstart for HttpGateway ------------------------------ Key: JBESB-2447 URL: https://jira.jboss.org/jira/browse/JBESB-2447 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.5 Reporter: Jim Ma -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-2425) BeanConfigActionProcessor swallows specialized exceptions

by Hudaverdi Cakir (JIRA)

BeanConfigActionProcessor swallows specialized exceptions --------------------------------------------------------- Key: JBESB-2425 URL: https://jira.jboss.org/jira/browse/JBESB-2425 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.5 Reporter: Hudaverdi Cakir The current implementation of BeanConfigActionProcessor catches at java.lang.Exception level and re-packages these exceptions into an ActionProcessingException. But when a particular Action throws a specialized exception, e.g. ActionProcessingFaultException, the information gets lost and the processing can not be controlled as desired. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBESB-2207) SqlTableGatewayListener does not support synchronous delivery.

by Tomasz Juchniewicz (JIRA)

SqlTableGatewayListener does not support synchronous delivery. -------------------------------------------------------------- Key: JBESB-2207 URL: https://jira.jboss.org/jira/browse/JBESB-2207 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Tomasz Juchniewicz -- 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-2100) InVM exception

by Joakim Sandström (JIRA)

InVM exception -------------- Key: JBESB-2100 URL: https://jira.jboss.org/jira/browse/JBESB-2100 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 Reporter: Joakim Sandström >From my forum post: My logs gets filled up with the following exception, any ideas what is wrong with my configuration? I'm using jboss-4.2.3.GA, jbossesb-4.4.GA, jboss messaging 1.4.0.SP3 and MySQL 5.0.67. 2008-10-07 05:07:20,334 DEBUG [org.jboss.internal.soa.esb.couriers.InVMCourier] InVMCourier for EPR 'invm://6f72646572636865636b437573746f6d657246455342/false?false#10000' is not activ e. Cannot pickup/deliver on this courier. java.lang.Exception at org.jboss.internal.soa.esb.couriers.InVMCourier.isCourierActive(InVMCourier.java:281) at org.jboss.internal.soa.esb.couriers.InVMCourier.pickup(InVMCourier.java:217) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:240) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:216) at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:280) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:248) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:619) JBoss esb generates about 1GB of logs each minute due to this error, about 800K of InVM errors. -- 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

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