4:42 p.m.
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:55 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
Brad Davis commented on JBESB-3724:
-----------------------------------
I actually think we could accomplish this with globally defined Acitons for the action
pipeline, where we could define the actions to be added to every action pipeline at both
the beginning and end of the service. This might be the cheapest time commitment for
ESB.
If we had that, we could implement the following fairly easily:
1) exception handling (since actions already support exception methods)
2) analytics by stamping message time information onto the message as one of the global
"head" actions, and reading that at a globally defined "tail" action
3) business activity monitoring by publishing notifications when a message arrives at a
service; each message could be stamped in the body with a stack of locations the message
had been to, and we could log that somewhere in the future for customers to see the path a
message took. This would be valuable from a logging and testing angle to developers as
well.
4) because actions get the service configuration when the action is instantiated, we could
probably get the listeners to register to a human-readable repository in the future.
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:55 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
Brad Davis updated JBESB-3724:
------------------------------
Comment: was deleted
(was: I actually think we could accomplish this with globally defined Acitons for the
action pipeline, where we could define the actions to be added to every action pipeline at
both the beginning and end of the service. This might be the cheapest time commitment for
ESB.
If we had that, we could implement the following fairly easily:
1) exception handling (since actions already support exception methods)
2) analytics by stamping message time information onto the message as one of the global
"head" actions, and reading that at a globally defined "tail" action
3) business activity monitoring by publishing notifications when a message arrives at a
service; each message could be stamped in the body with a stack of locations the message
had been to, and we could log that somewhere in the future for customers to see the path a
message took. This would be valuable from a logging and testing angle to developers as
well.
4) because actions get the service configuration when the action is instantiated, we could
probably get the listeners to register to a human-readable repository in the future.
)
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
Brad Davis commented on JBESB-3724:
-----------------------------------
We would need interceptors therefore for:
1) when the action pipeline is initially called
2) when the action pipeline execution is complete
3) when a service is instantiated
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:08 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-3724:
----------------------------------
Fix Version/s: 4.11
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:10 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3724:
-------------------------------------------
Bugzilla Update: Perform
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:10 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration updated JBESB-3724:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=784057
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:58 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
RH Bugzilla Integration commented on JBESB-3724:
------------------------------------------------
Rick Wagner <rwagner(a)redhat.com> made a comment on [bug
784057|https://bugzilla.redhat.com/show_bug.cgi?id=784057]
GSS has encountered this issue also. Prioritized 'High'.
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3724.
-----------------------------------
Resolution: Done
Interceptors can now be configured - the user should implement
org.jboss.soa.esb.listeners.message.PipelinInterceptor and configured the interceptors
with the interception points within jbossesb-properties.xml.
I've added interception points at service instantiation, service start, service end,
and service failure (see the properties below).
The PipelineInterceptor is passed a message and a ConfigTree. Please note that in the
case of the instantiation interceptor, no message has been passed in to the pipeline yet,
so a null message is passed back to the interceptor.
<properties name="interceptors">
<property name="org.jboss.soa.esb.pipeline.failure.interceptors"
value=""org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
<property name="org.jboss.soa.esb.pipeline.instantiate.interceptors"
value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
<property name="org.jboss.soa.esb.pipeline.start.interceptors"
value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
<property name="org.jboss.soa.esb.pipeline.end.interceptors"
value="org.jboss.soa.esb.listeners.message.GenericPipelineInterceptor"/>
</properties>
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.10
Reporter: Brad Davis
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:32 p.m.
[
https://issues.jboss.org/browse/JBESB-3724?page=com.atlassian.jira.plugin...
]
Tom Cunningham closed JBESB-3724.
---------------------------------
Assignee: Tom Cunningham
Global Action Pipeline Interceptor
----------------------------------
Key: JBESB-3724
URL: https://issues.jboss.org/browse/JBESB-3724
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4724
days inactive
4813
days old
9 comments
5 participants
participants (5)
-
Brad Davis (Commented) (JIRA) -
Brad Davis (Created) (JIRA)
-
Brad Davis (Updated) (JIRA)
-
RH Bugzilla Integration (JIRA)
-
Tom Cunningham (JIRA)