User: stark
Date: 01/01/16 19:43:36
Modified: documentation JMX.ExternalContext.HowTo.html
Log:
Add InitialContext documentation and change the erroneous MLET close
tag to mbean.
Revision Changes Path
1.2 +8 -2 newsite/documentation/JMX.ExternalContext.HowTo.html
Index: JMX.ExternalContext.HowTo.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/documentation/JMX.ExternalContext.HowTo.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- JMX.ExternalContext.HowTo.html 2001/01/14 01:43:54 1.1
+++ JMX.ExternalContext.HowTo.html 2001/01/17 03:43:36 1.2
@@ -28,7 +28,8 @@
<mbean code="org.jboss.naming.ExternalContext"
name="DefaultDomain:service=ExternalContext/ldap/dscape" >
<attribute name="JndiName">external/ldap/dscape</attribute>
<attribute name="Properties">dscape.ldap</attribute>
-</MLET>
+ <attribute
name="InitialContext">javax.naming.ldap.InitialLdapContext</attribute>
+</mbean>
</pre>
where:
<ul>
@@ -46,6 +47,11 @@
string in which case it is treated as a resource that can be loaded
via the current
thread's context class loader.
</li>
+ <li>InitialContext is the class name of the InitialContext class to
create. Should be one
+ of javax.naming.InitialContext,
javax.naming.directory.InitialDirContext, or
+ javax.naming.ldap.InitialLdapContext. In the case of the
InitialLdapContext, a null
+ Controls array is used.
+ </li>
</ul>
This example is binding an external LDAP context into the JBoss JNDI namespace under
the name "external/ldap/dscape". An example dscape.ldap properties file is:
@@ -76,7 +82,7 @@
The mbean tag looks like this:
<pre class="code" align="left">
<mbean code="org.jboss.naming.JNDIView" name="DefaultDomain:service=JNDIView"
>
-</MLET>
+</mbean>
There are no configurable attributes. This simply loads the mbean into the JBoss
server VM so that it can be used via the JMX MBean View.
</div>
