December 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, 9 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2174) org.milyn.routing.jms.JMSRouter is always creating a String message

by Jaroslaw Kijanowski (JIRA)

org.milyn.routing.jms.JMSRouter is always creating a String message ------------------------------------------------------------------- Key: JBESB-2174 URL: https://jira.jboss.org/jira/browse/JBESB-2174 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.4 CP1 Reporter: Jaroslaw Kijanowski When I use org.milyn.routing.jms.JMSRouter during splitting and routing I always end up with a String message, even if I set <param name="messageType">ObjectMessage</param> (instead of the default value "TextMessage"). The reason for this is the creation strategy. In smooks-1.0.1, ObjectMessageCreationStrategy creates an ObjectMessage by calling the object's toString() method: return session.createObjectMessage( object.toString() ); This looks fixed in smooks trunk: return session.createObjectMessage( 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, 9 months

4
5
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, 9 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-2230) Verify generated html images for docs

by Kevin Conner (JIRA)

Verify generated html images for docs ------------------------------------- Key: JBESB-2230 URL: https://jira.jboss.org/jira/browse/JBESB-2230 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 HTML export appears to reduce the quality of embedded images, to the point where it is no longer possible to understand any text. We need to verify all images when generated HTML for release. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2198) Re-export odt documents as PDF and verfiy that all images are also exported

by Daniel Bevenius (JIRA)

Re-export odt documents as PDF and verfiy that all images are also exported --------------------------------------------------------------------------- Key: JBESB-2198 URL: https://jira.jboss.org/jira/browse/JBESB-2198 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Daniel Bevenius Seem that images have not been exported when exporting the odt documents to pdf. I've just tried exporting the ProgrammersGuide.odt and images are being exported to the resulting pdf. -- 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, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-2179) Add Tomcat support for HTTP Gateway

by Mark Little (JIRA)

Add Tomcat support for HTTP Gateway ----------------------------------- Key: JBESB-2179 URL: https://jira.jboss.org/jira/browse/JBESB-2179 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Mark Little Assignee: Mark Little Fix For: 4.5 >From the LegStar work. -- 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, 9 months

5
13
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, 9 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, 10 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2008