whoops my bad .. ive got it..
this was sent by bruce tobin not long ago..
<snip>
I had a problem running the mdb example in the latest
jbosstest sources: the invoke() method in
MessageDrivenContainer.ContainerInterceptor threw a
null pointer exception which I eventually traced back
to the fact that the MethodInvocation had no
EnterpriseContext, which was in turn due to the
MessageDrivenInstanceInterceptor never being
instantiated. The underlying problem seems to be in
jbosstest/src/resources/mdb/META-INF/jboss.xml,
where the container-name is specified as "Default
MesageDriven Bean". This doesn't correspond to
anything in the standardjboss.xml shipped with the
latest jboss sources. When I globally substituted
"Standard Message Driven Bean" for "Default
MesageDriven Bean" in
jbosstest/src/resources/mdb/META-INF/jboss.xml,
everything seemed to work fine.
</snip>
ps: newbies! search archives before sending questions...that goes to me too ;)
.u
Rafizan Baharum wrote:
> hi
>
> im trying to do MDB. when i deploy ive got this error msg
>
> [Container factory] Deploying DebugTopicBean
> [Container factory] There are no interceptors configured. Check the
> standardjboss.xml file
>
> and i check standardjboss.xml it has the config to interceptor.. what's
> going on?
>
> .u
>
> ==========standardjboss.xml==================
> <container-configuration>
> <container-name>Standard Message Driven Bean</container-name>
> <call-logging>false</call-logging>
>
>
><container-invoker>org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker</container-invoker>
>
> <container-interceptors>
>
> <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
>
> <interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
> <!-- CMT -->
> <interceptor
> transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor>
>
> <interceptor transaction="Container"
> metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
>
> <interceptor
>
>transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
>
> <!-- BMT -->
> <interceptor
>
>transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor>
>
> <interceptor
> transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor>
>
> <interceptor transaction="Bean"
> metricsEnabled="true">org.jboss.ejb.plugins.MetricsInterceptor</interceptor>
>
> </container-interceptors>
>
> <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool>
>
> <instance-cache></instance-cache>
> <persistence-manager></persistence-manager>
>
> <transaction-manager>org.jboss.tm.TxManager</transaction-manager>
> <container-invoker-conf>
> <RMIObjectPort>4444</RMIObjectPort>
> <Optimized>True</Optimized>
> </container-invoker-conf>
> <container-pool-conf>
> <MaximumSize>100</MaximumSize>
> <MinimumSize>10</MinimumSize>
> </container-pool-conf>
> </container-configuration>
>
> Rafizan Baharum wrote:
>
> > hi,
> >
> > is the MDB working on the new snapshot(02/03)? i saw some comments that
> > say something like "this not working because it tests for durable topic"
> > in jbosstest's mdb
> >
> > im trying to intercept any CRUD operation on entity bean or the facade
> > session bean and log it to some JMS topic and this will be subscribed by
> > other remote subscriber. is this a good idea or should i use log4j
> > XxxAppender?
> >
> > TIA
> > .u
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > List Help?: [EMAIL PROTECTED]
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
