FW: [Fwd: Re: [JBoss-dev] jrmp invoker issue]

[Tom Elrod]

The standardjboss.xml has historically never had more than one invoker 
type specified, but agree that would be nice to have them all declared 
there so would be easier for people to swap out the one they want to use 
(or via deployment file, specify addition of others).

I would like to ask that the one used for the container-configuration 
elements remains the unified type for jbossas 5 (which can be changed 
out for testing different invokers).

Jaroslaw Kijanowski wrote:
> That's what I wanted to hear. So it's a bug, that the definition for the 
> jrmp invoker is missing in server/src/etc/conf/default/standardjboss.xml.
> I will add the following lines to the file, because they should be 
> present, right? We still want to be able to use jrmp invoker.
> ****************************************
>     <invoker-proxy-binding>
>       <name>stateless-rmi-invoker</name>
>       <invoker-mbean>jboss:service=invoker,type=jrmp</invoker-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 
> call-by-value="false">org.jboss.invocation.InvokerInterceptor</interceptor>
>             <interceptor 
> call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor</interceptor>
>           </home>
>           <bean>
>             
> <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>
> 
> ------------------------------------------------------------------------
> *From:* jboss-development-bounces at lists.jboss.org on behalf of Scott M Stark
> *Sent:* Wed 2006-08-30 12:32
> *To:* JBoss.org development list
> *Subject:* Re: FW: [Fwd: Re: [JBoss-dev] jrmp invoker issue]
> 
> An ejb container can have multiple invokers, only the container
> configuration has one default. All standard invokers should have an
> invoker-proxy-binding defined in the standardjboss.xml descriptor so
> that it can easily be used in deployment jboss.xml descriptors to add an
> invoker to a deployment container or change the default for a container
> configuration.
> 
> Tom Elrod wrote:
>  > Not sure I understand your suggestion.  An ejb 2.x container can only
>  > have *one* invoker specified (as only one can be used at any point in
>  > time).  The standardjboss.xml is the file where which invoker to use
>  > is specified.  Maybe you mean keep all three invokers declared (in the
>  > jboss-service.xml) so that all three start up and are available for
>  > use.  Then to change which one gets used can by simply changing which
>  > one is referenced in the standardjboss.xml?
>  >
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>