July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-749) Invalid events in bpm_orchestration1 and bpm_orchestration2 samples

by Jiri Pechanec (JIRA)

Invalid events in bpm_orchestration1 and bpm_orchestration2 samples ------------------------------------------------------------------- Key: JBESB-749 URL: http://jira.jboss.com/jira/browse/JBESB-749 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM, Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Jiri Pechanec Assigned To: Mark Little Priority: Optional The start nodes in both examples have attached actions on node-enter event. According to jBPM source code, this event is not supported on start node and thus not fired. Recommended solution Attach the action to node-leave event -- 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
6
0 / 0

[JBoss JIRA] Created: (JBESB-724) PackageJMSMessageContents should set the appropriate ESB Message body content to the type of JMSMessage being packaged

by Daniel Bevenius (JIRA)

PackageJMSMessageContents should set the appropriate ESB Message body content to the type of JMSMessage being packaged ----------------------------------------------------------------------------------------------------------------------- Key: JBESB-724 URL: http://jira.jboss.com/jira/browse/JBESB-724 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor The current implementation of PackageJmsMessageContent will always package the content of a JMSMessage as a byte array. This has the effect of the JMSRouter's property 'unwrap' extract the contents of the ESB Message object but always send a JMS message of type BytesMessage. Try to find a way to add this "typing" of the ESB Message contents so that I doesn't break clients the depend on it. This sort of packaging/unpacking of JMSMessages could be extracted into a separate class so that the same logic is used whenever this is needed (like in NotifyJMS, JMSRouter ). -- 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

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-705) deadletter quickstart modifications

by Kevin Conner (JIRA)

deadletter quickstart modifications ----------------------------------- Key: JBESB-705 URL: http://jira.jboss.com/jira/browse/JBESB-705 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Kevin Conner Assigned To: Mark Little Priority: Minor Fix For: 4.2 Milestone Release 3 The quickstart demonstrates a failing service but also attempts to display the contents of the DLQ after the action has failed. Unfortunately the DLQ may not contain the failing message at the time the CheckMessageStoreAction is executed. Example output from two runs is as follows 10:45:06,517 INFO [STDOUT] Show all messages in the messageStore with category DLQ 10:45:06,518 INFO [DBMessageStoreImpl] retrieved 0 undelivered messages 10:45:29,839 INFO [STDOUT] Show all messages in the messageStore with category DLQ 10:45:29,843 INFO [DBMessageStoreImpl] retrieved 1 undelivered messages 10:45:29,843 INFO [STDOUT] *********** 10:45:29,843 INFO [STDOUT] Hello Dead Message - Tue Jul 17 10:45:05 BST 2007 The message in the second run is the failed message from the first run. This needs documenting or fixing. -- 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-674) Service name and Action name should be unique

by Tom Cunningham (JIRA)

Service name and Action name should be unique --------------------------------------------- Key: JBESB-674 URL: http://jira.jboss.com/jira/browse/JBESB-674 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2 Need to make the service name unique within a .esb file. Need to make an action name unique within an <actions> chain of a service. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-571) Next release should be against AS 4.2.

by Mark Little (JIRA)

Next release should be against AS 4.2. -------------------------------------- Key: JBESB-571 URL: http://jira.jboss.com/jira/browse/JBESB-571 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.2 -- 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
12
0 / 0

[JBoss JIRA] Created: (JBESB-677) Make sure we use the EAP branch of AS 4.2 and not the community version.

by Mark Little (JIRA)

Make sure we use the EAP branch of AS 4.2 and not the community version. ------------------------------------------------------------------------ Key: JBESB-677 URL: http://jira.jboss.com/jira/browse/JBESB-677 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Packaging Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Kurt Stam -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBESB-676) Replace manual service invocation with ServiceInvoker code

by Tom Fennelly (JIRA)

Replace manual service invocation with ServiceInvoker code ---------------------------------------------------------- Key: JBESB-676 URL: http://jira.jboss.com/jira/browse/JBESB-676 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 This is related to JBESB-575 which couldn't be completed because of the state of code at the time. There are still places in our code where we are manually looking up EPRs, looping over Couriers etc. This has all been encapsulated in the ServiceInvoker class. -- 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

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-709) jbpm CommandInterpreter action fails silently within doTheJob

by Kevin Conner (JIRA)

jbpm CommandInterpreter action fails silently within doTheJob ------------------------------------------------------------- Key: JBESB-709 URL: http://jira.jboss.com/jira/browse/JBESB-709 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Kevin Conner Assigned To: Mark Little The doTheJob method of CommandInterpreter wraps all exception within the body of the current message. These values appear to be ignored as errors do not terminate processing. -- 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-576) Hot redeployment documentation

by Mark Little (JIRA)

Hot redeployment documentation ------------------------------ Key: JBESB-576 URL: http://jira.jboss.com/jira/browse/JBESB-576 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Mark Little Assigned To: Kevin Conner Priority: Critical Fix For: 4.2 Make sure our docs on hot redeployment are sufficient. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBESB-462) Oracle AQ JMS Provider

by Burr Sutter (JIRA)

Oracle AQ JMS Provider ---------------------- Key: JBESB-462 URL: http://jira.jboss.com/jira/browse/JBESB-462 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 JBoss ESB needs to be tested with Oracle AQ as the JMS provider implementation. -- 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
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007