November 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1389) Resolve discrepencies between SOA platform branch and CP branch

by Kevin Conner (JIRA)

Resolve discrepencies between SOA platform branch and CP branch --------------------------------------------------------------- Key: JBESB-1389 URL: http://jira.jboss.com/jira/browse/JBESB-1389 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.2.1 CP1 There are a number of changes that have been committed into the SOA platform branch, some of which are applied on behalf of the platform and others appear to be project related. We need to go through all the differences and make sure that any project related changes are backported into CP (and then trunk). -- 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, 2 months

2
6
0 / 0

[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, 2 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, 2 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, 2 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, 2 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, 2 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, 2 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1325) Autoconfigure jndi-URL in jms-provider when it is not specified

by Martin Vecera (JIRA)

Autoconfigure jndi-URL in jms-provider when it is not specified --------------------------------------------------------------- Key: JBESB-1325 URL: http://jira.jboss.com/jira/browse/JBESB-1325 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.2.1 Reporter: Martin Vecera Priority: Critical We need a behaviour where the server_address in the jndi-URL attribute (<jms-provider jndi-URL="server_address"> in jboss-esb.xml) is configured automatically on deployment when no such attribute is specified. It should be configured to contain the address of the server on which you are deploying the ESB archive. It is critical for cluster testing. -- 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, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBESB-1297) Mark EPRs in registry as ESB-aware (or not)

by Mark Little (JIRA)

Mark EPRs in registry as ESB-aware (or not) ------------------------------------------- Key: JBESB-1297 URL: http://jira.jboss.com/jira/browse/JBESB-1297 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.3 Currently the JBR gateway registers itself in the registry with an ESB-unaware EPR (socket or HTTP) and this gets picked up by the ServiceInvoker, which complains because it can't use it to find a valid Courier. -- 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, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2007