Thanks a lot for the information.
By the same way, if I have to implement and deploy my own server side JBOSSMQ
interceptors, should I have to implement
org.jboss.mq.server.JMSServerInterceptor or extend
org.jboss.mq.server.JMSServerInterceptorSupport, that are deployed as a JBoss
service and
If I understand your question correctly, you somewhat answered it yourself.
As far as basic java rule of thumb, if you can reuse some of the functionality,
then extend, otherwise re-implement. However, since you are providing
another interceptor your inharitance comes from adding (before,
Following is my understading.
They need to be AOP interceptors (implement org.jboss.aop.advice.Interceptor).
Also, an AOP configuration file that specifies the AOP bindings must be
available in the client classpath.
Please correct me if my undersanding is wrong.
Thanks.
View the original
You can use any AOP framework (i.e., AspectJ etc). What I was trying to say,
there is no JBoss provided Client Container(Proxy) with a configurable
interceptor stack, something you see in JBoss EJB implementation where you have
concepts like Client Side and Server Side with coresponding
There is no client side interceptors in JBossMQ.
However, you can use any AOP framework (i.e. JBossAOP etc.) to aspectize (write
an interceptor or an aspect) your class (which I assume could be JMS client).
Regards
View the original post :
