October 2014 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3728) New logging action with detailed debug and trace output

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3728?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3728: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 813873|https://bugzilla.redhat.com/show_bug.cgi?id=813873] from VERIFIED to CLOSED > New logging action with detailed debug and trace output > ------------------------------------------------------- > > Key: JBESB-3728 > URL: https://issues.jboss.org/browse/JBESB-3728 > Project: JBoss ESB > Issue Type: Enhancement > Components: Rosetta, Tooling > Affects Versions: 4.11 > Reporter: Noel O'Connor > Assignee: Tom Cunningham > Priority: Minor > Fix For: 4.11 > > Attachments: ServiceLoggerAction.java > > > A new logging action which can be added to the action list and will output data depending on the logging level chosen. > It has a dependency on commons-lang -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3708) XsltAction cannot handle org.w3c.dom.Document

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3708?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3708: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 781101|https://bugzilla.redhat.com/show_bug.cgi?id=781101] from VERIFIED to CLOSED > XsltAction cannot handle org.w3c.dom.Document > --------------------------------------------- > > Key: JBESB-3708 > URL: https://issues.jboss.org/browse/JBESB-3708 > Project: JBoss ESB > Issue Type: Bug > Components: Rosetta > Affects Versions: 4.10 > Reporter: David Tucker > Assignee: Tom Cunningham > Fix For: 4.11 CP1 > > > Currently the XsltAction can handle the following objects: > String, byte[], Reader, InputStream, File, or Source > The output from the XsltAction, when choosing DOM, is an object that implements the interface org.w3c.dom.Document. The action can't accept the document it created to run another transformation on it. While this scenario is remote at best, it is not unlikely that we would want to run a transformation on a Document. I was able to create a custom action that would allow me to put a Document into a DOMSource object. This requires extra work anytime I want to use a Document in an XSLT and the Document interface should be an accepted way of sending a document to be transformed. The following code was all it took in my custom action: > DOMSource domSource = new DOMSource(); > domSource.setNode(doc.getFirstChild()); //doc is an object implementing org.w3c.dom.Document -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3758) RecordRoute functionality on both service and message basis

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3758?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3758: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 813872|https://bugzilla.redhat.com/show_bug.cgi?id=813872] from VERIFIED to CLOSED > RecordRoute functionality on both service and message basis > ----------------------------------------------------------- > > Key: JBESB-3758 > URL: https://issues.jboss.org/browse/JBESB-3758 > Project: JBoss ESB > Issue Type: Feature Request > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 > > > Provide new, optional configuration options for ESB services to specify that the > message header should be updated upon service entry and service exit. This > allows users to track the history of the message through a set of services to see > what path it took. Reasonable default value to capture is the service name. This > is not intended to be a routing ticket. > Comments: A suggestion would be to include a 'record route' option for a service and > message, placing the information within the message context. The information > should start with the originator (service, gateway, client) and add other services > as the message progresses. We already have the EntryExitTimeFilter and > GatewayFilters, I'm sure it would be easy to extend their functionality and link in > to the current service information. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3828) JbpmService should not call JbpmConfiguration.close

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3828?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3828: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 783951|https://bugzilla.redhat.com/show_bug.cgi?id=783951] from VERIFIED to CLOSED > JbpmService should not call JbpmConfiguration.close > --------------------------------------------------- > > Key: JBESB-3828 > URL: https://issues.jboss.org/browse/JBESB-3828 > Project: JBoss ESB > Issue Type: Bug > Components: Process flow > Affects Versions: 4.11 CP1 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3833) Lifecycle resources need to handle redeploy using same ClassLoader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3833?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3833: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 783951|https://bugzilla.redhat.com/show_bug.cgi?id=783951] from VERIFIED to CLOSED > Lifecycle resources need to handle redeploy using same ClassLoader > ------------------------------------------------------------------ > > Key: JBESB-3833 > URL: https://issues.jboss.org/browse/JBESB-3833 > Project: JBoss ESB > Issue Type: Bug > Components: Rosetta > Affects Versions: 4.11 > Reporter: Kevin Conner > Assignee: Kevin Conner > Fix For: 4.11 CP1 > > > ESB artifacts can go through a redeployment (stop, destroy, create, start) without replacing the ClassLoader. As such the lifecycle resources will be marked as destroyed and will no longer be usable. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3724) Global Action Pipeline Interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3724: ------------------------------------------------ Douglas Palmer <dpalmer(a)redhat.com> changed the Status of [bug 784057|https://bugzilla.redhat.com/show_bug.cgi?id=784057] from VERIFIED to CLOSED > Global Action Pipeline Interceptor > ---------------------------------- > > Key: JBESB-3724 > URL: https://issues.jboss.org/browse/JBESB-3724 > Project: JBoss ESB > Issue Type: Feature Request > Components: Configuration > Affects Versions: 4.10 > Reporter: Brad Davis > Assignee: Tom Cunningham > Fix For: 4.11 > > > We would like to have the capability to intercept prior to the action pipeline the Message, globally. This will lay the foundation for being able to hook in global interceptors for global exception handling, business activity monitoring, and service analytics. > When the interceptor is executed for the service, it would be helpful to send in not just the Message, but information on the current service (name, etc) as well. This may include which adapter the message is arriving on, what the service name and category is, etc. We have tried in the past to create something like this for a client using AOP, but couldn't achieve it this way, as JBoss AOP has some serious limitations in the Enterprise offerings. > It would be also great if the interceptor had the capability to read the full configuration of the service to know what listeners are provided. This could be used in the future to log inputs for services to a service registry. > In addition to the hooks for this in the Action Pipeline code, we would also need to have a globally defined configuration for interceptors. > The background behind this request is that often times, clients need to do analytics over service request / response times, or need to globally define rules for Exception Handling, or need to intercept input and output messages for auditing. We are hoping that this feature would facilitate all of these by allowing Red Hat to start shipping generic implementations for these things incrementally, and also enabling customers to craft their own to meet specific business needs. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3975) Hawt.io only shows broker config from version 1.0

by Geert Schuring (JIRA)

[ https://issues.jboss.org/browse/JBESB-3975?page=com.atlassian.jira.plugin... ] Geert Schuring commented on JBESB-3975: --------------------------------------- I see I should have created this item in the ENTESB project: https://issues.jboss.org/browse/ENTESB Could someone with the proper rights move this issue to that project? Thanks. > Hawt.io only shows broker config from version 1.0 > ------------------------------------------------- > > Key: JBESB-3975 > URL: https://issues.jboss.org/browse/JBESB-3975 > Project: JBoss ESB > Issue Type: Bug > Environment: jboss-fuse-6.1.0.redhat-379 > Reporter: Geert Schuring > Labels: broker, config, console, hawt.io, management, versions > > The MQ tab in the Hawt.io interface of a Fabric based Fuse setup only shows broker configurations found in version 1.0. > We have added a broker config in version 4.0 which is invisible to Hawt.io. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3975) Hawt.io only shows broker config from version 1.0

by Geert Schuring (JIRA)

Geert Schuring created JBESB-3975: ------------------------------------- Summary: Hawt.io only shows broker config from version 1.0 Key: JBESB-3975 URL: https://issues.jboss.org/browse/JBESB-3975 Project: JBoss ESB Issue Type: Bug Environment: jboss-fuse-6.1.0.redhat-379 Reporter: Geert Schuring The MQ tab in the Hawt.io interface of a Fabric based Fuse setup only shows broker configurations found in version 1.0. We have added a broker config in version 4.0 which is invisible to Hawt.io. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2014