October 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2063) JBESB-454 reversed: input-suffix is required

by Ryan Hochstetler (JIRA)

JBESB-454 reversed: input-suffix is required -------------------------------------------- Key: JBESB-2063 URL: https://jira.jboss.org/jira/browse/JBESB-2063 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Ryan Hochstetler JBESB-454 modified AbstractFileGateway and to permit the omission of the input-suffix on a fs-message-filter. This appears to have been undone in changeset 14322 by using ConfigTree.getRequiredAttribute() which throws .... Caused by: org.jboss.soa.esb.ConfigurationException: Required configuration property 'inputSuffix' not defined on config uration 'listener'. at org.jboss.soa.esb.helpers.ConfigTree.getRequiredAttribute(ConfigTree.java:242) at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.checkMyParms(AbstractFileGateway.java:313) at org.jboss.soa.esb.listeners.gateway.AbstractFileGateway.<init>(AbstractFileGateway.java:89) at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.<init>(FileGatewayListener.java:45) I tried working around the issue by providing a single space as the input-suffix. This generated a different exception: ... Caused by: org.jboss.soa.esb.ConfigurationException: Must specify postProcessSuffix at org.jboss.soa.esb.listeners.gateway.FileGatewayListener$IgnoreFile.<init>(FileGatewayListener.java:218) at org.jboss.soa.esb.listeners.gateway.FileGatewayListener.<init>(FileGatewayListener.java:68) ... 52 more I specified a post processing suffix by adding the post-suffix attribute ( meaningless since I had specifed post-delete="true") to the fs-message-listener element, but I still received the same exception complaining about the lack of a postProcessSuffix. While it may seem simple enough to just change AbstractFileGateway.java:313 to call ConfigTree.getAttribute(), I think that there is a deeper issue since the FileGatewayListener.IgnoreFileFilter fails to construct, even though I'm providing the requested attribute (which has a hard-coded default....). sample config: <fs-bus busid="foo_gw" > <fs-message-filter directory="/h/data/foos" work-suffix=".esbWorking" post-delete="true" error-directory="/h/data/foos/error" error-suffix=".error" /> </fs-bus> -- 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
7
0 / 0

[JBoss JIRA] Created: (JBESB-1721) Add MSSQL config files

by Martin Vecera (JIRA)

Add MSSQL config files ---------------------- Key: JBESB-1721 URL: http://jira.jboss.com/jira/browse/JBESB-1721 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Registry and Repository Affects Versions: 4.2.1 CP2 Reporter: Martin Vecera Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2.1 CP3 Add following configuration files to support MSSQL: deploy/jbossesb.esb/message-store-sql/mssql deploy/jbossesb.sar/juddi-sql/mssql deploy/jbossesb.sar/lib/juddi-2.0rc5.jar/juddi-sql/mssql For juddi we are experimenting with files copied from sybase config. The server is able to start with that. We will know more after running the tests. -- 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
15
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-1711) ESB unit test suite hangs when run against SOA-P CP1

by Aleksandar Kostadinov (JIRA)

ESB unit test suite hangs when run against SOA-P CP1 ---------------------------------------------------- Key: JBESB-1711 URL: http://jira.jboss.com/jira/browse/JBESB-1711 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Aleksandar Kostadinov Assigned To: Aleksandar Kostadinov unzip SOA-P distribution in $WORKSPACE/jbosssoa chprop product.properties org.jboss.esb.server.home "$WORKSPACE/jbosssoa/jboss-as" chprop product.properties org.jboss.esb.server.config $SERVER_NAME chprop product.properties org.jboss.esb.test.ftp.hostname dev39.qa.atl.jboss.com chprop product.properties org.jboss.esb.test.ftp.user user chprop product.properties org.jboss.esb.test.ftp.pwd pass chprop product.properties org.jboss.esb.test.ftp.dir /esb-in-soa then: cd product ant org.jboss.esb.integration.test Test suite hangs after first few tests. -- 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

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2052) EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET

by Burr Sutter (JIRA)

EBWS: WSDL produced by ESB Based Web Service endpoint is not consumable by .NET ------------------------------------------------------------------------------- Key: JBESB-2052 URL: https://jira.jboss.org/jira/browse/JBESB-2052 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Burr Sutter The WSDL and the quickstart that creates it are attached. Here is the exact error message from Visual Studio/Visual Basic: Error 1 Custom tool error: Unable to import WebService/Schema. Unable to import binding 'FetchCustomerBinding' from namespace 'http://soa.jboss.org/ESBWebServiceSample'. The operation 'FetchCustomerOp' on portType 'FetchCustomerPortType' from namespace 'http://soa.jboss.org/ESBWebServiceSample' had the following syntax error: The operation has no matching binding. Check if the operation, input and output names in the Binding section match with the corresponding names in the PortType section. C:\Users\Burr\AppData\Local\Temporary Projects\WindowsApplication1\My Project\Settings.settings 1 1 WindowsApplication1 -- 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

4
13
0 / 0

[JBoss JIRA] Created: (JBESB-2141) Document client automatical XA transaction enlistment

by Martin Vecera (JIRA)

Document client automatical XA transaction enlistment ----------------------------------------------------- Key: JBESB-2141 URL: https://jira.jboss.org/jira/browse/JBESB-2141 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Rosetta, Transports Affects Versions: 4.4 Reporter: Martin Vecera ESB client (e.g. ServiceInvoker) always uses XA transaction when sending JMS message using JBM. This automatic transaction enlistment should be documented. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1958) JBoss Remoting Gateway not providing HTTP query string in composed message

by Tom Fennelly (JIRA)

JBoss Remoting Gateway not providing HTTP query string in composed message -------------------------------------------------------------------------- Key: JBESB-1958 URL: https://jira.jboss.org/jira/browse/JBESB-1958 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Tom Fennelly Fix For: 4.x This happens because the JBR CoyoteInvoker doesn't forward the query string in the request parameters 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

17 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-2049) Check for invalid synchronous invocations within a transactional context

by Kevin Conner (JIRA)

Check for invalid synchronous invocations within a transactional context ------------------------------------------------------------------------ Key: JBESB-2049 URL: https://jira.jboss.org/jira/browse/JBESB-2049 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Kevin Conner We support a number of transports which integrate with transactions in a manner such that the delivery of the message will not occur until the transaction has been committed. If these transports are used to delivery a synchronous message then the result is a timeout/failure. We should introduce a mechanism where we can identify these situations and throw a different exception, clarifying the failure for our users. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2003) Allow configuration of async redelivery property on a per message basis

by Kevin Conner (JIRA)

Allow configuration of async redelivery property on a per message basis ----------------------------------------------------------------------- Key: JBESB-2003 URL: https://jira.jboss.org/jira/browse/JBESB-2003 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.5 The codebase allows for this property to be set through the global properties but does not (officially) allow it to be set per invocation. -- 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, 4 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 October 2008