August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-947) propertiesFromSelector cannot handle extra whitespace within expression

by Kevin Conner (JIRA)

propertiesFromSelector cannot handle extra whitespace within expression ----------------------------------------------------------------------- Key: JBESB-947 URL: http://jira.jboss.com/jira/browse/JBESB-947 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Priority: Trivial Fix For: 4.2.1 The Util.propertiesFromSelector method expects single spaces to be used within an expression, it cannot handle multiple spaces. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBESB-926) Come up with a better name for the "Contract" Application

by Tom Fennelly (JIRA)

Come up with a better name for the "Contract" Application --------------------------------------------------------- Key: JBESB-926 URL: http://jira.jboss.com/jira/browse/JBESB-926 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management, Registry and Repository Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1, 5.0 Milestone Release 1 We need a better name for this application. What I find most odd/dangerous about it is the webapp context name of "contract". So the URL ends up being "http://localhost:8080/contract". I'd prefer it to be something like "http://localhost:8080/jbossesb-endpoints" or just "http://localhost:8080/esb-endpoints". -- 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
2
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, 8 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, 8 months

3
15
0 / 0

[JBoss JIRA] Created: (JBESB-917) Need a distributed management web application for management

by Tom Cunningham (JIRA)

Need a distributed management web application for management ------------------------------------------------------------ Key: JBESB-917 URL: http://jira.jboss.com/jira/browse/JBESB-917 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Reporter: Tom Cunningham Assigned To: Mark Little Fix For: 4.2.1 Splitting off the management portion of JBESB-738 into its own bug. -- 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-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, 8 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-786) Change Gateways so they don't always use the byte[] portion of Messages

by Mark Little (JIRA)

Change Gateways so they don't always use the byte[] portion of Messages ----------------------------------------------------------------------- Key: JBESB-786 URL: http://jira.jboss.com/jira/browse/JBESB-786 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: Mark Little Sometimes byte[] may make sense, but for a lot of cases it simply doesn't. For example, using setByteArray for sending back a String! For incoming messages (small 'm') we could allow for header encoding within the received stream that indicates how the message (small 'm') should then we encapsulated within the ESB as a Message. That would mean we wouldn't convert all incoming byte streams as byte streams in the ESB either. -- 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

1
2
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-773) Make the Message.Body location to which SmooksTransformer binds Java objects configurable...

by Tom Fennelly (JIRA)

Make the Message.Body location to which SmooksTransformer binds Java objects configurable... -------------------------------------------------------------------------------------------- Key: JBESB-773 URL: http://jira.jboss.com/jira/browse/JBESB-773 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.2 Milestone Release 3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 At the moment they get bound to "EXTRACTED_BEANS_HASH", which was a terrible name. I must have been smoking some of the stuff at the time or something :-) -- 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

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007