November 2015 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-805) Implement some of the meta-data aspects of EPRs

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-805?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-805. ----------------------------- Resolution: Out of Date > Implement some of the meta-data aspects of EPRs > ----------------------------------------------- > > Key: JBESB-805 > URL: https://issues.jboss.org/browse/JBESB-805 > Project: JBoss ESB > Issue Type: Feature Request > Components: Rosetta > Affects Versions: 4.2 Milestone Release 3 > Reporter: Mark Little > Assignee: Mark Little > > At least the ability to add the service name/contract info. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-1934) Message filters configurable at archive/service level

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-1934?page=com.atlassian.jira.plugin... ] Mark Little closed JBESB-1934. ------------------------------ Resolution: Out of Date > Message filters configurable at archive/service level > ----------------------------------------------------- > > Key: JBESB-1934 > URL: https://issues.jboss.org/browse/JBESB-1934 > Project: JBoss ESB > Issue Type: Feature Request > Components: Rosetta > Affects Versions: 4.4 > Reporter: Martin Vecera > Assignee: Mark Little > > It would be great if message filters (described in linked issue) could be configured at least at archive level (service level would be better). Have it configured globally for all the services doesn't have much sense IMHO. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-986) ContentBasedRouter action complains for missing destinations

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-986?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-986. ----------------------------- Resolution: Done > ContentBasedRouter action complains for missing destinations > ------------------------------------------------------------ > > Key: JBESB-986 > URL: https://issues.jboss.org/browse/JBESB-986 > Project: JBoss ESB > Issue Type: Bug > Components: Content Based Routing, Rosetta > Affects Versions: 4.2.1 > Reporter: Jiri Pechanec > Assignee: Mark Little > Priority: Minor > > The ContentBasedRouter is subcalss of ContentBasedWiretap. This class complains during the initialization - Missing or empty destination list - This action class won't have any effect. If the action is used not for routing but for message modification according to business rules (see e.g. business_rules_service quickstart) then it behaves as false alarm. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

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

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-817?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-817. ----------------------------- Resolution: Out of Date > Rename Message to Envelope? > --------------------------- > > Key: JBESB-817 > URL: https://issues.jboss.org/browse/JBESB-817 > Project: JBoss ESB > Issue Type: Task > Components: Documentation, Rosetta > Affects Versions: 4.2 Milestone Release 3 > Reporter: Mark Little > Assignee: 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 was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

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

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-823?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-823. ----------------------------- Resolution: Done > Separate DLQ from Message Store > ------------------------------- > > Key: JBESB-823 > URL: https://issues.jboss.org/browse/JBESB-823 > Project: JBoss ESB > Issue Type: Feature Request > Components: Message Store > Affects Versions: 4.2 Milestone Release 3 > Reporter: Mark Little > Assignee: 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 was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-667) Echo action

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-667?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-667. ----------------------------- Resolution: Done > Echo action > ----------- > > Key: JBESB-667 > URL: https://issues.jboss.org/browse/JBESB-667 > Project: JBoss ESB > Issue Type: Feature Request > Components: Rosetta > Affects Versions: 4.2 Milestone Release 2 > Reporter: Mark Little > Assignee: 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 was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

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

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-819?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-819. ----------------------------- Resolution: Done > Give example of context use > --------------------------- > > Key: JBESB-819 > URL: https://issues.jboss.org/browse/JBESB-819 > Project: JBoss ESB > Issue Type: Task > Components: Documentation, Examples > Affects Versions: 4.2 Milestone Release 3 > Reporter: Mark Little > Assignee: 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 was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-777) Create some wiki pages around SOA patterns for the ESB

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-777?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-777. ----------------------------- Resolution: Done > Create some wiki pages around SOA patterns for the ESB > ------------------------------------------------------ > > Key: JBESB-777 > URL: https://issues.jboss.org/browse/JBESB-777 > Project: JBoss ESB > Issue Type: Feature Request > Components: Documentation > Reporter: Mark Little > Assignee: Mark Little > Priority: Critical > > Ones that don't rely on exposing individual objects on to the bus. Conform to recognised SOA patterns. > It'll be hard without all of the supporting tools, but it's still possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-280) Gateway listeners cannot be registered under the same name as their message aware counterparts

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-280?page=com.atlassian.jira.plugin.... ] Mark Little closed JBESB-280. ----------------------------- Resolution: Done > Gateway listeners cannot be registered under the same name as their message aware counterparts > ---------------------------------------------------------------------------------------------- > > Key: JBESB-280 > URL: https://issues.jboss.org/browse/JBESB-280 > Project: JBoss ESB > Issue Type: Bug > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assignee: Mark Little > Priority: Optional > > The Gateways need to be registered under a completely different name than the message aware "Service " listener they are fronting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-1692) Need a quickstart that demonstrates Filters

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBESB-1692?page=com.atlassian.jira.plugin... ] Mark Little closed JBESB-1692. ------------------------------ Resolution: Done > Need a quickstart that demonstrates Filters > ------------------------------------------- > > Key: JBESB-1692 > URL: https://issues.jboss.org/browse/JBESB-1692 > Project: JBoss ESB > Issue Type: Feature Request > Components: Examples > Reporter: Burr Sutter > Assignee: Mark Little > Priority: Minor > > From the Programmers Guide > The class org.jboss.soa.esb.filter.InputOutputFilter has two methods: > ? public Message onOutput (Message msg, Map<String, Object> params) throws > CourierException which is called as a message flows to the transport. An implementation > may modify the message and return a new version. Additional information may be provided > by the caller in the form of extra parameters. > ? public Message onInput (Message msg, Map<String, Object> params) throws > CourierException which is called as a message flows from the transport. An implementation > may modify the message and return a new version. Additional information may be provided > by the caller in the form of extra parameters. > Filters are defined in the filters section of the jbossesb-properties.xml file using the property > org.jboss.soa.esb.filter.<number>, where <number> can be any value and is used to > indicate the order in which multiple filters are to be called (lowest to highest). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2015