Bill Why is it that we need to specify a client interceptor configuration per JRMP invoker again? I know there was a good reason when you were discussing with Francisco but I can't remember.
aren't these stand-alone, refered to by name and a bean can say "use these?" independently of the invoker configuration? marcf |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED]]On Behalf Of Bill |Burke |Sent: Sunday, April 21, 2002 12:03 AM |To: Jboss-Dev |Subject: [JBoss-dev] multiple invoker configuration | | |Okay, I've had some time to start working on multiple invokers per |container. Here's what the config looks like. I'm too tired to explain, |but you should be able to understand it by the example below. | |standardjboss.xml: | |*NOTE* <client-interceptors> is removed from container-configuration | |<jboss> | <invoker-configurations> | <invoker-configuration> | <name>entity-rmi-invoker</name> | <mbean>jboss:service=invoker,type=jrmp</mbean> | <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory> | <proxy-factory-config> | <client-interceptors> | <home> | <interceptor>org.jboss.proxy.ejb.HomeInterceptor</interceptor> | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> | |<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> | |<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> | </home> | <bean> | |<interceptor>org.jboss.proxy.ejb.EntityInterceptor</interceptor> | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> | |<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> | |<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> | </bean> | <list-entity> | |<interceptor>org.jboss.proxy.ejb.ListEntityInterceptor</interceptor> | <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor> | |<interceptor>org.jboss.proxy.TransactionInterceptor</interceptor> | |<interceptor>org.jboss.invocation.InvokerInterceptor</interceptor> | </list-entity> | </client-interceptors> | </proxy-factory-config> | </invoker-configuration> |.... |.... | |jboss.xml: |<entity> | <ejb-name>ClusterEJB</ejb-name> | <invoker-bindings> | <invoker> | <invoker-name>entity-iiop-invoker</invoker-name> | <jndi-name>IIOPCustomer</jndi-name> | </invoker> | <invoker> | <invoker-name>entity-rmi-invoker</invoker-name> | <jndi-name>Customer</jndi-name> | </invoker> | <invoker-bindings> |.... |.... | |If no invoker-binding is defined, then the default will be |entity-rmi-invoker and top-level or default jndi-name will be used. | | |Regards, | |Bill | | |_______________________________________________ |Jboss-development mailing list |[EMAIL PROTECTED] |https://lists.sourceforge.net/lists/listinfo/jboss-development _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
