September 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1076) Unify composer approach for gateways

by Mark Little (JIRA)

Unify composer approach for gateways ------------------------------------ Key: JBESB-1076 URL: http://jira.jboss.com/jira/browse/JBESB-1076 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters, Documentation Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little The File gateways use the MessageComposer for creating Messages from input data, whereas the other gateways use a reflective approach. We should standardise on one approach for gateways. Then update the Adapters documentation. -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-782) Some of the unit tests are misnamed

by Mark Little (JIRA)

Some of the unit tests are misnamed ----------------------------------- Key: JBESB-782 URL: http://jira.jboss.com/jira/browse/JBESB-782 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little The testing name structure we agreed on was **UnitTest.java and **IntegrationTest.java. However, some of the unit tests are misnamed, e.g., MessageStoreTest.java -- 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, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-819) Give example of context use

by Mark Little (JIRA)

Give example of context use --------------------------- Key: JBESB-819 URL: http://jira.jboss.com/jira/browse/JBESB-819 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little >From our intern: "Context is pretty important to maintaining loosely-coupled sessions. Can you give an example of how it might be used in the ESB?" -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-860) Have the jcr jackrabbit store implement the full MessageStore interface

by Kurt Stam (JIRA)

Have the jcr jackrabbit store implement the full MessageStore interface ----------------------------------------------------------------------- Key: JBESB-860 URL: http://jira.jboss.com/jira/browse/JBESB-860 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 The jcr implementation has some methods stubbed out. For extra credits we can should have it implement the RedeliverStore interface too, -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-667) Echo action

by Mark Little (JIRA)

Echo action ----------- Key: JBESB-667 URL: http://jira.jboss.com/jira/browse/JBESB-667 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Add an echo Action that simply send back the same message to the sender. Could be used for heart-beat, but also for distributed management. -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-823) Separate DLQ from Message Store

by Mark Little (JIRA)

Separate DLQ from Message Store ------------------------------- Key: JBESB-823 URL: http://jira.jboss.com/jira/browse/JBESB-823 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little The Message Store was intended to logging, debugging etc. It keeps track of what's on the wire. We're now using it for the retry/retransmit and DLQ. Even if the same backend implementation were used, shouldn't that be a separate service? DLQ is for reliability, whereas the Message Store implementation isn't necessarily reliable or available to users, e.g., an organisation may not want to expose it's Message Store details to the world for security reasons, but a general DLQ may be supported by the ESB for reliability reasons. -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-817) Rename Message to Envelope?

by Mark Little (JIRA)

Rename Message to Envelope? --------------------------- Key: JBESB-817 URL: http://jira.jboss.com/jira/browse/JBESB-817 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little On behalf of our intern: "Wouldn't it be better to call Message Envelope? It might avoid some confusion too amongst WS-* and JMS developers." -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-948) Look at ArjName approach for logical names

by Mark Little (JIRA)

Look at ArjName approach for logical names ------------------------------------------ Key: JBESB-948 URL: http://jira.jboss.com/jira/browse/JBESB-948 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-697) Add loop-back transport.

by Mark Little (JIRA)

Add loop-back transport. ------------------------ Key: JBESB-697 URL: http://jira.jboss.com/jira/browse/JBESB-697 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little -- 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, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-1105) ESB Should have a good load generation framework

by James Williams (JIRA)

ESB Should have a good load generation framework ------------------------------------------------ Key: JBESB-1105 URL: http://jira.jboss.com/jira/browse/JBESB-1105 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Environment: I have created groovy scripts that simulate load and provide some TPS metrics. I used an external Groovy 1.1-Beta as my test for these scripts. Groovy is bootstrapped in the build script, so it's possible to swap it out with the ESB bundled, but I do not know if I'm doing any 1.1 specific stuff. Reporter: James Williams Assigned To: James Williams Priority: Minor There are 2 groovy scripts. One script, JMSLoadAgent.groovy, simulates load by dropping sample messages into a JMS gateway. There are a slew of properties entries to control the throttling of messages, and the payload file can be specified outside of the groovy script. This script is designed to be a template for other load scripts. For example, a load script that drops files into a directory that has a file system listener. The 2nd script, LoadReport.groovy, uses the JMX MBean stats at the service level to report TPS. you can specify one or more services as a comma separated list. And, there is a short circuit that will kill the reporter. The short cut is a bit crude, but it works. You specify the fastest ESB listener queue. When that queue depth is at 0, the report stops. The report will print out to the console, and to a properties file configured location. There are also several ant targets to run either the agent, reporter or both. I also include a sample ESB archive to test the quickstart and the services are hardwired so that one is distinctively faster than the other. These scripts should work for any service, provided the user adds the proper entries to "load.properties". There is no GUI for this yet, but I started out with a GUI, then realized that primary benefit of the load framework is the stats dumped into a log file or on the console. All other stuff is pretty straightforward with a simple properties file. The readme.txt probably needs a little beef, but I'm going to go ahead and check this in because I think it's going to be a very valuable contribution for users looking to load test and identify TPS at the service level. -- 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, 11 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2007