January 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2181) Add findugs coverage into ESB 4

by Kevin Conner (JIRA)

Add findugs coverage into ESB 4 ------------------------------- Key: JBESB-2181 URL: https://jira.jboss.org/jira/browse/JBESB-2181 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.4 Reporter: Kevin Conner 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, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-2302) Wise NullPointerException in SOAPClient

by Kevin Conner (JIRA)

Wise NullPointerException in SOAPClient --------------------------------------- Key: JBESB-2302 URL: https://jira.jboss.org/jira/browse/JBESB-2302 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 CP1 Reporter: Kevin Conner Assignee: Daniel Bevenius Fix For: 4.4 CP2 The current wise SOAPClient does not check to see whether the soapAction actually references a method in the WSDL and, as a consequence, the following code can lead to a NullPointerException. result = wsmethodsMap.get(this.soapAction).invoke(params, mapper); We need to add a check for this part and provide a meaningful error message. -- 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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2224) Add UDP listener support

by Tom Fennelly (JIRA)

Add UDP listener support ------------------------ Key: JBESB-2224 URL: https://jira.jboss.org/jira/browse/JBESB-2224 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Reporter: Tom Fennelly Fix For: 4.5 Add UDP listener support. Some work has already been done on this: https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/sandbox/iplistener. In this, the listener is hooked in using a groovy scripted gateway (<groovy-listener>). -- 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, 3 months

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-849) Should smooks test be an integration test?

by Mark Little (JIRA)

Should smooks test be an integration test? ------------------------------------------ Key: JBESB-849 URL: http://jira.jboss.com/jira/browse/JBESB-849 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Fennelly Priority: Trivial [java] [junit] 10:22:35,254 ERROR [main][SmooksInstanceManager] Lookup of the JMS ConnectionFactory failed for the Transformation configuration Update Listener. Update listener not enabled! [java] [junit] org.jboss.soa.esb.ConfigurationException: JNDI lookup of JMS Connection Factory [ConnectionFactory] failed. [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.getJmsConnectionFactory(SmooksInstanceManager.java:161) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.connect(SmooksInstanceManager.java:203) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:122) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager$ConfigurationUpdateListener.<init>(SmooksInstanceManager.java:109) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksInstanceManager.<init>(SmooksInstanceManager.java:67) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialiseLocalSmooksInstanceManager(SmooksTransformer.java:236) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformer.initialise(SmooksTransformer.java:218) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.transform(SmooksTransformerUnitTest.java:82) [java] [junit] at org.jboss.soa.esb.actions.converters.SmooksTransformerUnitTest.test_trans(SmooksTransformerUnitTest.java:69) indicates that the test needs JMS set up beforehand. So doesn't that tend to imply it's an integration test? -- 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

17 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-2099) missing line from org.jboss.soa.esb.message.Body example in programmers guide

by Darrin Mison (JIRA)

missing line from org.jboss.soa.esb.message.Body example in programmers guide ----------------------------------------------------------------------------- Key: JBESB-2099 URL: https://jira.jboss.org/jira/browse/JBESB-2099 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 Reporter: Darrin Mison Priority: Minor Chapter 3 has a code sample showing the interface declaration of org.jboss.soa.esb.message.Body it is missing public String[] getNames() -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2296) diagram missing from ESB Programmers Guide

by Darrin Mison (JIRA)

diagram missing from ESB Programmers Guide ------------------------------------------ Key: JBESB-2296 URL: https://jira.jboss.org/jira/browse/JBESB-2296 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Darrin Mison On page 62 of the ESB Programmers guide the Fault classification hierarchy diagram has been deleted from. See http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/docs/Prog... I would say that this was an accidental as the text still refers to it. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Closed: (JBESB-427) Roll-your-own Gateway example and docs

by Mark Little (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-427?page=com.atlassian.jira.plug... ] Mark Little closed JBESB-427. ----------------------------- Fix Version/s: 4.5 Resolution: Done Done by Tom Fennelly. > Roll-your-own Gateway example and docs > -------------------------------------- > > Key: JBESB-427 > URL: https://jira.jboss.org/jira/browse/JBESB-427 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Documentation, Rosetta > Reporter: Mark Little > Assignee: Mark Little > Fix For: 4.5 > > > Provide enough infrastructure and documentation so the end-user of our ESB can relatively easily add their own gateway/listener (BC) to a proprietary protocol that they wish to enable. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2175) ftp-message-filter: add support for the 'post-rename' attribute

by Daniel Bevenius (JIRA)

ftp-message-filter: add support for the 'post-rename' attribute --------------------------------------------------------------- Key: JBESB-2175 URL: https://jira.jboss.org/jira/browse/JBESB-2175 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Configuration Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.5 The ftp-message-filter should support the 'post-rename' attribute like the fs-message-filter does. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Updated: (JBESB-354) Addition of a helloworld_sftp_action in the quickstarts

by Kevin Conner (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-354?page=com.atlassian.jira.plug... ] Kevin Conner updated JBESB-354: ------------------------------- Fix Version/s: 4.4 CP3 (was: 4.4 CP2) > Addition of a helloworld_sftp_action in the quickstarts > ------------------------------------------------------- > > Key: JBESB-354 > URL: https://jira.jboss.org/jira/browse/JBESB-354 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assignee: Kevin Conner > Priority: Minor > Fix For: 4.4 CP3 > > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2287) DefaultJMSPropertiesSetter should filter out provider specific properties when performing the mapping

by Tom Fennelly (JIRA)

DefaultJMSPropertiesSetter should filter out provider specific properties when performing the mapping ----------------------------------------------------------------------------------------------------- Key: JBESB-2287 URL: https://jira.jboss.org/jira/browse/JBESB-2287 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP1, 4.4 Reporter: Tom Fennelly Fix For: 4.5 Vendor Specific Properties: ===================== "The JMS API reserves the JMS_vendor_name property name prefix for provider-specific properties. Each provider defines its own value for vendor_name. This is the mechanism a JMS provider uses to make its special per-message services available to a JMS client. The purpose of provider-specific properties is to provide special features needed to integrate JMS clients with provider-native clients in a single JMS application. They should not be used for messaging between JMS clients." JBossMQ definitely doesn't like these properties being mapped onto its messages. I've seen it in a situation where the JMSGateway was running on WebsphereMQ and the messages are then routed to a message aware listener on JBossMQ. My guess is that JBM is not as sensitive. Stack trace: org.jboss.soa.esb.listeners.message.MessageDeliverException: Caught (un)marshal related exception during attempted send/receive. at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:595) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:492) at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:346) at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:233) at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:275) at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:243) at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doRun(JmsGatewayListener.java:175) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to set JMS Message properties from ESB Message properties. at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:210) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189) at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:571) ... 8 more Caused by: javax.jms.JMSException: Illegal property name: JMS_IBM_PutApplType at org.jboss.mq.SpyMessage.checkProperty(SpyMessage.java:996) at org.jboss.mq.SpyMessage.setIntProperty(SpyMessage.java:715) at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setProperties(DefaultJMSPropertiesSetter.java:161) at org.jboss.soa.esb.notification.jms.DefaultJMSPropertiesSetter.setJMSProperties(DefaultJMSPropertiesSetter.java:80) at org.jboss.internal.soa.esb.couriers.JmsCourier.setJMSProperties(JmsCourier.java:476) at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:208) ... 10 more -- 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, 3 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2009