Replacing JBossMQ interceptor in Jboss Messaging?

[afshanz]

Hi ,
I would like to know how do you set up your interceptor(JbossMQ interceptor) in new Jboss messaging?
Do you have any example for that and setup *-service.xml?

-Afshan

[ovidiu.feodorov]

Take a look at aop-messaging-client.xml and aop-messaging-server.xml. These files contain the client-side and server-side aspect stack configuration.

[ovidiu.feodorov]

No "canned" example yet, sorry. If you are willing to provide one, we will ship it with the distribution (http://jira.jboss.org/jira/browse/JBMESSAGING-208)

[afshanz]

Ovidiu,
We use this configuration in JbossMQ interceptor , we would like to keep the same order and invokation in stack.

<!-- ==================================================================== -->
<!-- JBossMQ Interceptor chain configuration -->
<!-- ==================================================================== -->
<!-- To tune performance, you can have the Invoker skip over the TracingInterceptor -->
<!-- and/or the SecurityManager, but then you loose the ability to trace and/or enforce security. -->

<depends optional-attribute-name="NextInterceptor">jboss.mq:service=SamClientLogin



com.timetra.nms.server.core.session.SamClientLoginInterceptor
<depends optional-attribute-name="NextInterceptor">jboss.mq:service=MapServiceClientInterceptor



com.timetra.nms.map.notification.MapServiceClientInterceptor
<depends optional-attribute-name="NextInterceptor">jboss.mq:service=SamJMSInterceptor



com.timetra.nms.server.j2ee.jms.SamJMSInterceptor
<depends optional-attribute-name="NextInterceptor">jboss.mq:service=TracingInterceptor



org.jboss.mq.server.TracingInterceptor
<depends optional-attribute-name="NextInterceptor">jboss.mq:service=SecurityManager