[EJB 3.0] - EJB3 container configuration and interceptors
by fakeer
how can i add custom interceptors in ejb3??
with ejb2 i have been using the standardjboss.xml to insert my own interceptors into the standard container interceptor stack (see ActivityInterceptor below). i also used a client side invocation interceptor to make some client information ride with the invocation payload (further below)
with my beans no on ejb3 the stadardjboss.xml configuration is just ignored? is there a new container configuration file for ejb3? i'm cluless
server side interceptor
| <container-configuration>
| <container-name>Standard Stateless SessionBean</container-name>
| <call-logging>false</call-logging>
| <invoker-proxy-binding-name>stateless-rmi-invoker</invoker-proxy-binding-name>
| <container-interceptors>
| <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
| <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
| <!-- CMT -->
| <interceptor>com.test.server.ejb.ActivityInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Container" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.webservice.server.ServiceEndpointInterceptor</interceptor>
| <interceptor transaction="Container">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
| <!-- BMT -->
| <interceptor transaction="Bean">org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.TxInterceptorBMT</interceptor>
| <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor>
| <interceptor transaction="Bean" metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
| <interceptor transaction="Bean">org.jboss.webservice.server.ServiceEndpointInterceptor</interceptor>
| <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor>
| </container-interceptors>
| <instance-pool>org.jboss.ejb.plugins.StatelessSessionInstancePool</instance-pool>
| <instance-cache></instance-cache>
| <persistence-manager></persistence-manager>
| <container-pool-conf>
| <MaximumSize>100</MaximumSize>
| </container-pool-conf>
| </container-configuration>
|
client side interceptor
| <invoker-proxy-binding>
| <name>stateless-rmi-invoker</name>
| <invoker-mbean>jboss:service=invoker,type=https</invoker-mbean>
| <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
| <proxy-factory-config>
| <client-interceptors>
| <home>
| <interceptor>com.test.client.ActivityClientInterceptor</interceptor>
| <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
| </home>
| <bean>
| <interceptor>com.test.client.ActivityClientInterceptor</interceptor>
| <interceptor>org.jboss.proxy.ejb.StatelessSessionInterceptor</interceptor>
| <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
| <interceptor>org.jboss.proxy.TransactionInterceptor</interceptor>
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
| </bean>
| </client-interceptors>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
thnx
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976441#3976441
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976441
19 years, 7 months
[Messaging, JMS & JBossMQ] - EKB 3.0 MDB not getting messages
by whartung
(Note, I inadvertantly posted this on the Jboss Messaging topic, but then realized it should probably be here.)
I have a simple SessionBean trying to send a message to a simple MDB.
The session bean "succeeds" in sending the message, but the MDB is not getting the message.
I put "succeeds" in quotes because all I can safely say is that I'm not getting an exception when I send the message, but when I look at the jboss.mq.DestinationManager using the JMX console, it doesn't show any message traffic.
Relevant bits from the the SessionBean:
| Connection connection = null;
| @Resource(mappedName = "ConnectionFactory")
| private ConnectionFactory connectionFactory;
| @Resource
| private SessionContext sc;
| @Resource(mappedName = "jms/MirthMessageMDB")
| private Queue queue;
|
| session = connection.createSession(true, 0);
| publisher = session.createProducer(queue);
| message = session.createObjectMessage();
|
| message.setObject(payload);
| publisher.send(message);
|
Relevant bits from the MDB.
| @MessageDriven(mappedName = "jms/MirthMessageMDBx",
| activationConfig = {
| @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
| @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")})
|
And relevant bits from my config:
| <mbean code="org.jboss.mq.server.jmx.Queue" name="jboss.mq.destination:service=Queue,name=mirth">
| <attribute name="JNDIName">jms/MirthMessageMDB</attribute>
| <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
| </mbean>
|
Everything runs quietly. I get no exceptions.
I added:
| <category name="org.jboss.mq">
| <priority value="TRACE" class="org.jboss.logging.XLevel"/>
| </category>
| <category name="org.jboss.jms">
| <priority value="TRACE" class="org.jboss.logging.XLevel"/>
| </category>
| <category name="org.jboss.ejb.plugins.jms">
| <priority value="TRACE" class="org.jboss.logging.XLevel"/>
| </category>
|
To conf/log4j.xml, but I'm not seeing any activity about these in the log.
I also see "jms/MirthMessageMDB" in the JNDI view of the JMX console.
I've tried renaming the queue in the config, and my SessionBean fails appropriately because it can't find the queue to inject in to it, but the MDB seems to deploy even with the badly named queue.
So, I'm a bit flumoxed. Any suggestions on moving forward appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976435#3976435
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976435
19 years, 7 months