[jboss-cvs] JBossAS SVN: r96938 - trunk/server/src/etc/conf/web.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Wed Nov 25 04:00:12 EST 2009


Author: scott.stark at jboss.org
Date: 2009-11-25 04:00:12 -0500 (Wed, 25 Nov 2009)
New Revision: 96938

Modified:
   trunk/server/src/etc/conf/web/jboss-service.xml
Log:
JBAS-6948, remove all beans from the web conf/jboss-service.xml.

Modified: trunk/server/src/etc/conf/web/jboss-service.xml
===================================================================
--- trunk/server/src/etc/conf/web/jboss-service.xml	2009-11-25 08:54:47 UTC (rev 96937)
+++ trunk/server/src/etc/conf/web/jboss-service.xml	2009-11-25 09:00:12 UTC (rev 96938)
@@ -14,94 +14,5 @@
    -->
    <classpath codebase="${jboss.server.lib.url}" archives="*"/>
    <classpath codebase="${jboss.common.lib.url}" archives="*"/>
-   
-   <!-- ==================================================================== -->
-   <!-- JNDI                                                                 -->
-   <!-- ==================================================================== -->
-   
-   <!-- A simple mbean wrapper around the jndi Naming object. This
-      only handles an in memory instance. The NamingService uses this
-      as the JNDI store and exposes it remotely.
-   -->
-   <mbean code="org.jnp.server.NamingBeanImpl"
-      name="jboss:service=NamingBeanImpl"
-      xmbean-dd="resource:xmdesc/NamingBean-xmbean.xml">
-   </mbean>
-   
-   <mbean code="org.jboss.naming.NamingService"
-      name="jboss:service=Naming"
-      xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
-      <!-- The call by value mode. true if all lookups are unmarshalled using
-         the caller's TCL, false if in VM lookups return the value by reference.
-      -->
-      <attribute name="CallByValue">false</attribute>
-      
-      <!-- The listening port for the bootstrap JNP service. Set this to -1
-         to run the NamingService without the JNP invoker listening port.
-      -->
-      <attribute name="Port">
-         <value-factory bean="ServiceBindingManager" method="getIntBinding">
-            <parameter>jboss:service=Naming</parameter>
-            <parameter>Port</parameter>
-         </value-factory>
-      </attribute>
-      
-      <!-- The bootstrap JNP server bind address. This also sets the default
-         RMI service bind address. Empty == all addresses
-      -->
-      <attribute name="BindAddress">
-         <value-factory bean="ServiceBindingManager" method="getStringBinding">
-            <parameter>jboss:service=Naming</parameter>
-            <parameter>Port</parameter>
-            <parameter><null/></parameter>
-         </value-factory>
-      </attribute>
-      
-      <!-- The port of the RMI naming service, 0 == anonymous -->
-      <attribute name="RmiPort">
-         <value-factory bean="ServiceBindingManager" method="getIntBinding">
-            <parameter>jboss:service=Naming</parameter>
-            <parameter>RmiPort</parameter>
-         </value-factory>
-      </attribute>
-      <!-- The RMI service bind address. Empty == all addresses  -->
-      <attribute name="RmiBindAddress">
-         <value-factory bean="ServiceBindingManager" method="getStringBinding">
-            <parameter>jboss:service=Naming</parameter>
-            <parameter>RmiPort</parameter>
-            <parameter><null/></parameter>
-         </value-factory>
-      </attribute>
-      
-      <!-- The thread pool service used to control the bootstrap lookups -->
-      <attribute name="LookupPool">
-         <inject bean="LongRunningTasksThreadPool"/>
-      </attribute>
-      <!-- An example of using the unifed invoker as the transport.
-         <depends optional-attribute-name="InvokerProxyFactory"
-         proxy-type="attribute">jboss:service=proxyFactory,type=unified,target=Naming</depends>
-      -->
-      <depends optional-attribute-name="Naming"
-         proxy-type="attribute">jboss:service=NamingBeanImpl</depends>
-   </mbean>
-   
-   <!-- Writes the bootstrap URL for the NamingService in a known location,
-      so tools (e.g. Jopr) can use it as a java.naming.provider.url.
-   -->
-   <mbean code="org.jboss.naming.NamingProviderURLWriter"
-      name="jboss:service=NamingProviderURLWriter"
-      xmbean-dd="resource:xmdesc/NamingProviderURLWriter-xmbean.xml">
-      
-      <attribute name="Server"><inject bean="JBossServer"/></attribute>
-      <attribute name="BootstrapAddress"><inject bean="jboss:service=Naming" property="bindAddress"/></attribute>
-      <attribute name="BootstrapPort"><inject bean="jboss:service=Naming" property="port"/></attribute>
-   </mbean>
-   
-   <mbean code="org.jboss.naming.JNDIView"
-      name="jboss:service=JNDIView"
-      xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
-      <!-- The HANamingService service name -->
-      <attribute name="HANamingService">jboss:service=HAJNDI</attribute>
-   </mbean>
-   
+
 </server>




More information about the jboss-cvs-commits mailing list