[jboss-jira] [JBoss JIRA] Created: (JBAS-5226) ClientUserTransaction should be configured with Unified invoker

[Galder Zamarreno (JIRA)]

ClientUserTransaction should be configured with Unified invoker
---------------------------------------------------------------

                 Key: JBAS-5226
                 URL: http://jira.jboss.com/jira/browse/JBAS-5226
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
    Affects Versions: JBossAS-4.2.2.GA
            Reporter: Galder Zamarreno
         Assigned To: Galder Zamarreno
            Priority: Minor


Even though unified invokers are default for EJBs, 
jboss:service=ClientUserTransaction service is still using
JRMP invokers by default. ClientUserTransaction 
service definition should be changed to used unified 
invokers as below:

  <!--
     | UserTransaction support.
   -->
  <mbean code="org.jboss.tm.usertx.server.ClientUserTransactionService"
     name="jboss:service=ClientUserTransaction"
     xmbean-dd="resource:xmdesc/ClientUserTransaction-xmbean.xml">
     <depends>
        <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
           name="jboss:service=proxyFactory,target=ClientUserTransactionFactory">
           <!-- attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute -->
           <attribute name="InvokerName">jboss:service=invoker,type=unified</attribute>
           <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
           <attribute name="JndiName">UserTransactionSessionFactory</attribute>
           <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory</attribute>
           <attribute name="ClientInterceptors">
              <interceptors>
                 <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
                 <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
              </interceptors>
           </attribute>
           <!-- depends>jboss:service=invoker,type=jrmp</depends -->
           <depends>jboss:service=invoker,type=unified</depends>
        </mbean>
     </depends>
     <depends optional-attribute-name="TxProxyName">
        <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
           name="jboss:service=proxyFactory,target=ClientUserTransaction">
           <!-- attribute name="InvokerName">jboss:service=invoker,type=jrmp</attribute -->
           <attribute name="InvokerName">jboss:service=invoker,type=unified</attribute>
           <attribute name="TargetName">jboss:service=ClientUserTransaction</attribute>
           <attribute name="JndiName"></attribute>
           <attribute name="ExportedInterface">org.jboss.tm.usertx.interfaces.UserTransactionSession</attribute>
           <attribute name="ClientInterceptors">
              <interceptors>
                 <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
                 <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
              </interceptors>
           </attribute>
           <!-- depends>jboss:service=invoker,type=jrmp</depends -->
           <depends>jboss:service=invoker,type=unified</depends>
        </mbean>
     </depends>
  </mbean>

Bear in mind that even though ClientUserTransactionService uses JRMPProxyFactory, 
this is just a wrapper and you can set any type of invokers with it. You can indeed set 
the unified invoker as InvokerName.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira