September 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-591) SQL Listener should deal with rows

by Tom Cunningham (JIRA)

SQL Listener should deal with rows ---------------------------------- Key: JBESB-591 URL: http://jira.jboss.com/jira/browse/JBESB-591 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Mark Little Talked to Burr and Kurt today about the SQL poller quickstart and the SQL listener with regards to the hibernate listener. Burr thinks that the SQL listener should be dealing with the entire row as a message, rather than just a column. This would probably demand changes in both Listener and Quickstart. -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-629) Upgrade the Smooks console to use the newer config model

by Tom Fennelly (JIRA)

Upgrade the Smooks console to use the newer config model -------------------------------------------------------- Key: JBESB-629 URL: http://jira.jboss.com/jira/browse/JBESB-629 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Tooling, Transformation Service Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly It's currently using the Smooks v0.8 DTD based model. Upgrade it to use the newer v0.9 XSD based model. v0.9 is backward compatible with the v0.8 config model, but it throws out warnings (not exceptions) to the console. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1910) Smooks does not report error in configuration

by Jiri Pechanec (JIRA)

Smooks does not report error in configuration --------------------------------------------- Key: JBESB-1910 URL: https://jira.jboss.org/jira/browse/JBESB-1910 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.4 Reporter: Jiri Pechanec Fix For: 4.4 CP1 If the typo or wrong value in Smoks resource config, element resource the Smooks transformer did not complain for incorrect configuration. It just does not modify message payload. This can be particulary nast as it can take considerable amount of work to find where the problem is originating. -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1906) The stateful wokring memory should be unique per message correlation number

by Jiri Pechanec (JIRA)

The stateful wokring memory should be unique per message correlation number --------------------------------------------------------------------------- Key: JBESB-1906 URL: https://jira.jboss.org/jira/browse/JBESB-1906 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Critical Fix For: 4.4 CP1 For me it seems probably much more useful to provide also option to have stateful rule service organized on different basis. Each message should contain correlation identifier and the stateful session will be created per the correlation identifier. It will server much better the intent that is described in excerpt from Service documentation ----- These can be added directly by an ESB aware client. A non-ESB aware client would have to communicate the position of the message (first, ongoing, last) in the data, and an action class would need to be added to the pipeline to add the properties to the ESB message (see quickstarts/business_ruleservice_stateful for an example of this type of service). -- 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, 4 months

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

15 years, 4 months

2
8
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

15 years, 4 months

2
8
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

15 years, 4 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-1984) XSD validation in AbstractProcessingPipeline can fail in legacy environments

by Jiri Pechanec (JIRA)

XSD validation in AbstractProcessingPipeline can fail in legacy environments ---------------------------------------------------------------------------- Key: JBESB-1984 URL: https://jira.jboss.org/jira/browse/JBESB-1984 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Jiri Pechanec Priority: Critical In AbstractProcessingPipeline the message payload is accessed by direct call of message.get() for purpose of XSD validations. I thing the access should be via MessagePayloadProxy class as in other parts of the codebase to work correctly in legacy environment. -- 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, 4 months

2
11
0 / 0

[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

15 years, 4 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

15 years, 4 months

3
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2008