September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1010) Programmers Guide says that serialized message is the default type

by Mark Little (JIRA)

Programmers Guide says that serialized message is the default type ------------------------------------------------------------------ Key: JBESB-1010 URL: http://jira.jboss.com/jira/browse/JBESB-1010 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Priority: Trivial Fix For: 4.2.1 It's actually XML. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-869) Document reliability characteristics as far as message delivery is concerned

by Mark Little (JIRA)

Document reliability characteristics as far as message delivery is concerned ---------------------------------------------------------------------------- Key: JBESB-869 URL: http://jira.jboss.com/jira/browse/JBESB-869 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-932) Restructure documentation

by Mark Little (JIRA)

Restructure documentation ------------------------- Key: JBESB-932 URL: http://jira.jboss.com/jira/browse/JBESB-932 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.2.1 As per discussion with Joshua Wulf and Burr. -- 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, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-1000) Factor SOA text from Programmers Guide.

by Mark Little (JIRA)

Factor SOA text from Programmers Guide. --------------------------------------- Key: JBESB-1000 URL: http://jira.jboss.com/jira/browse/JBESB-1000 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 -- 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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-865) Separate Message Store text into Services document?

by Mark Little (JIRA)

Separate Message Store text into Services document? --------------------------------------------------- Key: JBESB-865 URL: http://jira.jboss.com/jira/browse/JBESB-865 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Message Store Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.2.1 On bahelf of intern: "Since the MessageStore text needs revisiting and the MessageStore interface seems to have increased in capabilities, wouldn't it make sense to separate it out of the Programmers Guide and into its own document, like the Registry and other services?" -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-910) Make JMSCourier set JMSHeader fields and properties when sending

by Daniel Bevenius (JIRA)

Make JMSCourier set JMSHeader fields and properties when sending ----------------------------------------------------------------- Key: JBESB-910 URL: http://jira.jboss.com/jira/browse/JBESB-910 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta, Transports Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor This jira is similar to http://jira.jboss.com/jira/browse/JBESB-691 The usecase for this would be when one has a router in the ESB pipeline configuration and the transport being JMS. Currently, having a router in the pipeline would mean losing the correlation id, and other properties that might have been set by a calling client. This can use the same code that JMSRouter and NotifyJMS uses. -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1018) exception in helloworld QS

by Jaroslaw Kijanowski (JIRA)

exception in helloworld QS -------------------------- Key: JBESB-1018 URL: http://jira.jboss.com/jira/browse/JBESB-1018 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jaroslaw Kijanowski Assigned To: Mark Little QS is from trunk: 22:22:28,047 INFO [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 22:22:28,047 INFO [STDOUT] Body: Hello World 22:22:28,049 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.ClassCastException: java.lang.String at org.jboss.soa.esb.samples.quickstart.helloworld.MyJMSListenerAction.displayMessage(MyJMSListenerAction.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) ... 6 more 22:22:28,049 WARN [ActionProcessingPipeline] No fault address defined for fault message! -- 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, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1025) Remove SampleObject from HelloWorld QS

by Mark Little (JIRA)

Remove SampleObject from HelloWorld QS -------------------------------------- Key: JBESB-1025 URL: http://jira.jboss.com/jira/browse/JBESB-1025 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 IR1 I added it when working on a new example based on HW. Should be a separate QS. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-701) JMS Queue Notifier does not have configured message properties attached

by Jiri Pechanec (JIRA)

JMS Queue Notifier does not have configured message properties attached ----------------------------------------------------------------------- Key: JBESB-701 URL: http://jira.jboss.com/jira/browse/JBESB-701 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 3 The configuration Notifier with class NotifyQueues can contain a list of elements "queue" and each of these "queue" can contain a list of "messageProp" elements that contains properties to be attached to message. The properties are not attached. The reason is: Constructor NotifyQueues is populated with ConfigTree that has root at the "target" element and has correctly access to the child "queue" elements from which it initilizes but the same ConfigTree is passed to NofityJMS parent class which can't initialize properties as they are stored not on this level but on the level below under each "queue" element. -- 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, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-956) ByteArrayToString does not use actionName

by Mark Little (JIRA)

ByteArrayToString does not use actionName ----------------------------------------- Key: JBESB-956 URL: http://jira.jboss.com/jira/browse/JBESB-956 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Tom Cunningham Fix For: 4.2.1 It's either needed or it isn't. The way it's currently set up, the actionName is passed in via the constructor but never used. This may mess up the uniqueness issue from earlier. -- 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, 2 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007