July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-601) Add a quickstart to demonstrate asynchronous invocations in jbpm

by Kevin Conner (JIRA)

Add a quickstart to demonstrate asynchronous invocations in jbpm ---------------------------------------------------------------- Key: JBESB-601 URL: http://jira.jboss.com/jira/browse/JBESB-601 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Kevin Conner Assigned To: Mark Little Priority: Minor 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

16 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-646) NON_PERSISTENT JMS messaging.

by Daniel Bevenius (JIRA)

NON_PERSISTENT JMS messaging. ----------------------------- Key: JBESB-646 URL: http://jira.jboss.com/jira/browse/JBESB-646 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assigned To: Mark Little Priority: Minor The current classes that deal with sending JMS messages, like JMSCourier, do not specify a delivery mode when sending messages. The default is then that the messages are sent with a delivery mode of persistent. The request (see forum reference) is to be able have the delivery mode configurable so one can avoid the persisting to stable storage. -- 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

16 years, 7 months

5
26
0 / 0

[JBoss JIRA] Created: (JBESB-704) business_rules_service QS does not function properly after redeployment

by Kevin Conner (JIRA)

business_rules_service QS does not function properly after redeployment ----------------------------------------------------------------------- Key: JBESB-704 URL: http://jira.jboss.com/jira/browse/JBESB-704 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little The business_rules_service does not function correctly after a redeployment. The first time the QS is executed you will receive output similar to the following 10:31:12,355 INFO [STDOUT] Customer Status: 60 10:31:12,355 INFO [STDOUT] Order Total: 44.92 10:31:12,355 INFO [STDOUT] { ================ After Order Priority 10:31:12,356 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60 10:31:12,356 INFO [STDOUT] Order Priority: 1 10:31:12,356 INFO [STDOUT] Order Discount: 0.0 10:31:12,356 INFO [STDOUT] Order Total: 44.92 10:31:12,356 INFO [STDOUT] } ================ After Order Priority 10:31:12,357 INFO [STDOUT] Customer Status: 60 10:31:12,358 INFO [STDOUT] Order Total: 44.92 10:31:12,358 INFO [STDOUT] { ================ After Order Discount 10:31:12,358 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60 10:31:12,358 INFO [STDOUT] Order Priority: 1 10:31:12,358 INFO [STDOUT] Order Discount: 0.0 10:31:12,358 INFO [STDOUT] Order Total: 44.92 10:31:12,358 INFO [STDOUT] } ================ After Order Discount 10:31:12,360 INFO [STDOUT] Low Priority 10:31:12,426 INFO [STDOUT] { ================ Shipping 10:31:12,426 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60 10:31:12,426 INFO [STDOUT] Order Priority: 1 10:31:12,426 INFO [STDOUT] Order Discount: 0.0 10:31:12,426 INFO [STDOUT] Order Total: 44.92 10:31:12,427 INFO [STDOUT] } ================ Shipping If you then redeploy the QS the output changes to the following 10:32:06,353 INFO [STDOUT] { ================ After Order Priority 10:32:06,354 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60 10:32:06,354 INFO [STDOUT] Order Priority: 1 10:32:06,354 INFO [STDOUT] Order Discount: 0.0 10:32:06,354 INFO [STDOUT] Order Total: 44.92 10:32:06,354 INFO [STDOUT] } ================ After Order Priority 10:32:06,356 INFO [STDOUT] { ================ After Order Discount 10:32:06,356 INFO [STDOUT] Customer: user1,Harry,Fletcher,SD,60 10:32:06,356 INFO [STDOUT] Order Priority: 1 10:32:06,356 INFO [STDOUT] Order Discount: 0.0 10:32:06,357 INFO [STDOUT] Order Total: 44.92 10:32:06,357 INFO [STDOUT] } ================ After Order Discount This appears to be the output from the ReviewMessage actions. -- 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

16 years, 7 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-626) Create a quickstart dedicated to demoing the External Webservice Consumption

by Tom Fennelly (JIRA)

Create a quickstart dedicated to demoing the External Webservice Consumption ---------------------------------------------------------------------------- Key: JBESB-626 URL: http://jira.jboss.com/jira/browse/JBESB-626 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples, Web Services Affects Versions: 4.2 Reporter: Tom Fennelly Assigned To: Tom Fennelly This feature is demo'd in the webservice_bpel quickstart, but there's also a number of other features demo'd there too (it's a bit more than a "quickstart"). It's be a good idea to have a quickstart dedicated to this feature. http://wiki.jboss.org/wiki/Wiki.jsp?page=ExternalWebserviceConsumption -- 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

16 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-730) Verify WS-Security support when running with SOAPProcessor Action

by Burr Sutter (JIRA)

Verify WS-Security support when running with SOAPProcessor Action ----------------------------------------------------------------- Key: JBESB-730 URL: http://jira.jboss.com/jira/browse/JBESB-730 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Refactor JBossWS Unit Tests that confirm support of WS-Security when using the ESB between the consumer and the producer via the SOAPProcessor Action -- 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

16 years, 8 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-733) bpm-based quickstarts should specify a businessKey for jBPM 3.2.1 Admin Console

by Burr Sutter (JIRA)

bpm-based quickstarts should specify a businessKey for jBPM 3.2.1 Admin Console ------------------------------------------------------------------------------- Key: JBESB-733 URL: http://jira.jboss.com/jira/browse/JBESB-733 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: BPM Affects Versions: 4.2 Milestone Release 2 Reporter: Burr Sutter Assigned To: Mark Little Fix For: 4.2 Without a businessKey set as a process instance variable (actual variable name still to be determined) the list of process instances looks all the same. Other than begin/end time it is impossible to differentiate between the various instances. The businessKey would normally bet set to something the Order/Invoice ID or some other unique but business related identifier. -- 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

16 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-590) Smooks processing of detached elements causing warning: Cannot count nodes before XXX has no parent

by Kevin Conner (JIRA)

Smooks processing of detached elements causing warning: Cannot count nodes before XXX has no parent --------------------------------------------------------------------------------------------------- Key: JBESB-590 URL: http://jira.jboss.com/jira/browse/JBESB-590 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Kevin Conner Assigned To: Tom Fennelly Fix For: 4.2 Smooks displays warning messages about its inability to count nodes of a detached element, this can be seen in the XML2POJO QS. The reason for the warning is that the element in question has been replaced by previous processing in AbstractTemplateProcessingUnit.processTemplateAction. The result of the replacement is that the original element is detached from the document but processing still continues as if it were present. -- 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

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-722) Hibernate interceptor unLoad event reports empty object

by Kevin Conner (JIRA)

Hibernate interceptor unLoad event reports empty object ------------------------------------------------------- Key: JBESB-722 URL: http://jira.jboss.com/jira/browse/JBESB-722 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2 The hibernate interceptor catches the preLoad event and uses the entity to create the message. Unfortunately, at this point, the entity is uninitialised with the exception of any primary keys. The entity state is located in the state/propertyNames/types arrays. We need to revisit this event to pass in meaningful information. -- 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

16 years, 8 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-628) Remove use of ThreadLocal in MessageDeliveryAdapter

by Tom Fennelly (JIRA)

Remove use of ThreadLocal in MessageDeliveryAdapter --------------------------------------------------- Key: JBESB-628 URL: http://jira.jboss.com/jira/browse/JBESB-628 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly This was only suppose to be a quick hack (by me), but I noticed today that I never went back and cleaned it up :-( -- 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

16 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-748) FTP couriers leak FTP connections

by Kevin Conner (JIRA)

FTP couriers leak FTP connections --------------------------------- Key: JBESB-748 URL: http://jira.jboss.com/jira/browse/JBESB-748 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The FTP Couriers are leaking FTP connections as they are never cleaned up. The easiest way to see this is to comment out the max-connection, max-login properties in the ftpd.properties file. -- 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

16 years, 8 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2007