[jboss-cvs] JBossCache/docs/JBossCache-UserGuide/en/modules ...

Brian Stansberry brian.stansberry at jboss.com
Tue May 29 23:08:46 EDT 2007


  User: bstansberry
  Date: 07/05/29 23:08:46

  Modified:    docs/JBossCache-UserGuide/en/modules  deployment.xml
  Log:
  JNDI binding is now a TODO
  
  Revision  Changes    Path
  1.6       +1 -41     JBossCache/docs/JBossCache-UserGuide/en/modules/deployment.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: deployment.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossCache/docs/JBossCache-UserGuide/en/modules/deployment.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -b -r1.5 -r1.6
  --- deployment.xml	30 May 2007 03:07:40 -0000	1.5
  +++ deployment.xml	30 May 2007 03:08:46 -0000	1.6
  @@ -52,47 +52,7 @@
   
         <section>
            <title>Binding to JNDI</title>
  -         <para>If JBoss Cache is run inside of JBoss AS (as an MBean), we can bind a
  -            proxy to it into JNDI using JrmpProxyFactory, just like any other MBean. Below is an
  -            example of how to do this:
  -            <programlisting>
  -               <![CDATA[
  -            <mbean code="org.jboss.invocation.jrmp.server.JRMPProxyFactory"
  -                  name="mydomain:service=proxyFactory,type=jrmp,target=factory">
  -                  
  -               <attribute name="InvokerName">jboss:service=invoker,type=unified</attribute>
  -               <attribute name="TargetName">jboss.cache:service=Cache</attribute>
  -               <attribute name="JndiName">MyCache</attribute> 
  -               <attribute name="InvokeTargetMethod">true</attribute> 
  -               <attribute name="ExportedInterface">org.jboss.cache.jmx.CacheJmxWrapperMBean</attribute>
  -               <attribute name="ClientInterceptors"> 
  -                  <interceptors>
  -                     <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
  -                     <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
  -                     <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
  -                  </interceptors> 
  -               </attribute>
  -               <depends>jboss:service=invoker,type=jrmp</depends>
  -               <depends>jboss.cache:service=Cache</depends>
  -            </mbean>
  -             ]]>
  -            </programlisting>
  -         </para>
  -
  -         <para>The
  -            <literal>InvokerName</literal>
  -            attribute needs to point to a
  -            valid JBoss invoker MBean.
  -            <literal>TargetName</literal>
  -            is the JMX name
  -            of the MBean that needs to be bound into JNDI.
  -            <literal>JndiName</literal>
  -            is the name under which the MBean will be
  -            bound.
  -         </para>
  -         <para>Clients (either in-VM or remote) can look up the proxy in JNDI,
  -         download the proxy and use it to invoke on the cache.
  -         </para>
  +         <para><emphasis>TODO</emphasis></para>
         </section>
   
      <section>
  
  
  



More information about the jboss-cvs-commits mailing list