April 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-502) Blocking Gateway - in and out.

by Kurt Stam (JIRA)

Blocking Gateway - in and out. ------------------------------ Key: JBESB-502 URL: http://jira.jboss.com/jira/browse/JBESB-502 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 I do think we should make an option for a blocking gateway, where the gateway waits for a a reply from an ESB Service. Basically we set the 'replyTO' on the message and route to a 'replyTO' service which replies back to the gateway. This is another argument for gateways to be in and out. -- 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

14 years, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default

by Tom Fennelly (JIRA)

Make action, listener etc configuration setting by setter method the default ---------------------------------------------------------------------------- Key: JBESB-476 URL: http://jira.jboss.com/jira/browse/JBESB-476 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 We currently configure everything by constructor. This is not great for a number of reasons: 1. It can't be compile time validated. 2. Not as "obvious" to someone developing against the API. If in an interface, their IDE (or at least compiler - if using a stone ax) will complain immediately that they're not implementing the interface correctly. 3. Makes our code a little bit more complicated re the reflection code that needs to be implemented. So I suggest making the interface (that all these things implement) contain a setter method that takes the config. The mandate on the implementation is that they contain a public default constructor. -- 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

14 years, 7 months

4
12
0 / 0

[JBoss JIRA] Created: (JBESB-511) Add integration test for default SFTP EPR.

by Mark Little (JIRA)

Add integration test for default SFTP EPR. ------------------------------------------ Key: JBESB-511 URL: http://jira.jboss.com/jira/browse/JBESB-511 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Rosetta, Testing Reporter: Mark Little Assigned To: Bruno Georges 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

15 years, 7 months

3
11
0 / 0

[JBoss JIRA] Created: (JBESB-506) Consider Mina support

by Mark Little (JIRA)

Consider Mina support --------------------- Key: JBESB-506 URL: http://jira.jboss.com/jira/browse/JBESB-506 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Reporter: Mark Little Assigned To: Mark Little Priority: Optional Fix For: 5.0 http://mina.apache.org/ -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-531) Scoped queue-service.xml's for quick starts

by Tom Cunningham (JIRA)

Scoped queue-service.xml's for quick starts ------------------------------------------- Key: JBESB-531 URL: http://jira.jboss.com/jira/browse/JBESB-531 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 1 Environment: Mac OS X, java 1.5.0_07 Reporter: Tom Cunningham Assigned To: Mark Little For the helloworld quick start we provide both a jbm-queue-service.xml and a jbm-queue-service-scoped.xml for deployment to different appservers. We should probably be consistent and supply this across the board. However, for the rest of the quickstart samples, we only supply a jbm-queue-service.xml. Also, maybe there should be an ant target which incorporates the scoped version of the xml? The jar target always seems to pick up the jbm-queue-service.xml (non-scoped) version. Also, the GettingStarted.pdf which covers the HelloWorld example doesn't talk about the situations where we'd want to use one version over the other. Should that be something that should be added to the 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-530) GettingStarted.pdf should be updated with service information

by Tom Cunningham (JIRA)

GettingStarted.pdf should be updated with service information ------------------------------------------------------------- Key: JBESB-530 URL: http://jira.jboss.com/jira/browse/JBESB-530 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 1, 4.2 Milestone Release 2 Environment: Mac OS X 10.4.9, java 1.5.0_07 Reporter: Tom Cunningham Assigned To: Mark Little The GettingStarted.pdf information on how to get the Hello World QuickStart working that seem old. Step 1 says "Copy samples/quickstarts/esb-quickstart-service.xml to your JBoss application server". In MR1, there isn't a esb-quickstart-service.xml, we have two service xml's, one for jboss-messaging and another for jboss-mq. There are: esb-quickstart-jbm-service.xml esb-quickstart-jbmq-service.xml There probably should be another step in there which explains how to install the jboss-messaging stuff if they want to use the esb-quickstart-jbm-service.xml 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

15 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBESB-520) convert quickstart readme.txt to readme.html to allow for links & images

by Burr Sutter (JIRA)

convert quickstart readme.txt to readme.html to allow for links & images ------------------------------------------------------------------------ Key: JBESB-520 URL: http://jira.jboss.com/jira/browse/JBESB-520 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 1 Reporter: Burr Sutter Assigned To: Jason Lenhart Priority: Minor Fix For: 4.2 Milestone Release 2 The main readme.txt should be converted to HTML, provide a brief description of each individual quickstart and actually link to that quickstart's readme.html. readme.html's might also include an image describing the architecture as well. -- 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

15 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-467) Reducing registry lookup overhead

by Mark Little (JIRA)

Reducing registry lookup overhead --------------------------------- Key: JBESB-467 URL: http://jira.jboss.com/jira/browse/JBESB-467 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta Affects Versions: 4.0 Reporter: Mark Little Assigned To: Kurt Stam Priority: Critical Fix For: 4.2, 5.0 >From our previous discussion on reducing registry lookup overhead (currently lookup per message send): There are a number of solutions to this and we should try to support them all eventually: (i) EPR lifetime: service deployers can register a lifetime associated with the EPR in the registry and when something reads the EPR it also receives information on how long the EPR will remain valid for. After that time elapses, clients must go back to the registry to get a new copy. (ii) building on (i), EPRs can be marked as persistent - they never change so one lookup will always be enough. (iii) interactions with services are scoped by sessions and the EPR is assumed to remain valid for the duration of the session. The service can be marked as useable within such a session. (iv) EPRs are looked up once per client lifecycle and only rebound if the service fails. If you recall from the original ESB architecture document, service migration is something that is on the roadmap (5.0) and if a service moves it can leave a forwarding address (EPR) and the architecture allows messages to be redirected and eventually short-cut, i.e., the client EPR is updated with the new EPR transparently as a result of receiving a response from a different endpoint. (iii) and (iv) are really for the 5.0 architecture. However, it should be possible to add something along (i) and (ii) for 4.0. What do you think? -- 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, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-498) Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware.

by Tom Fennelly (JIRA)

Allow Registry registrations to include a flag to indicate whether the endpoint is message aware/unaware. --------------------------------------------------------------------------------------------------------- Key: JBESB-498 URL: http://jira.jboss.com/jira/browse/JBESB-498 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 This will also mean adding query capability against this. This requirement could be generalised to simply allow registrations to be decorated with attributes, and have these same attributes returned in the lookups. -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-522) Controlled shutdown

by Kevin Conner (JIRA)

Controlled shutdown ------------------- Key: JBESB-522 URL: http://jira.jboss.com/jira/browse/JBESB-522 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Mark Little Fix For: 5.0 Milestone Release 1 During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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, 5 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2007