November 2008 - esb-issues - Jboss List Archives

[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

17 years, 2 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

17 years, 2 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

17 years, 2 months

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

17 years, 2 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

17 years, 2 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

17 years, 2 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

17 years, 2 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

17 years, 2 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

17 years, 2 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

17 years, 2 months

3
7
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2008