User: tobias
Date: 01/01/19 01:18:05
Modified: documentation HowTo.css JMX.Connector.Howto.html
JMX.ExternalContext.HowTo.html JMX.Timer.HowTo.html
ejb.html
Removed: documentation faq.htm faq.html
Log:
deleted useless files, fixed html errors
Revision Changes Path
1.4 +8 -0 newsite/documentation/HowTo.css
Index: HowTo.css
===================================================================
RCS file: /products/cvs/ejboss/newsite/documentation/HowTo.css,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- HowTo.css 2001/01/18 07:44:25 1.3
+++ HowTo.css 2001/01/19 09:18:04 1.4
@@ -5,6 +5,14 @@
BODY {
background-color:#99cc66;
}
+SPAN.page {
+ background-color:white;
+ margin-left:0.25in;
+ margin-right:0.25in;
+ margin-top:1em;
+ margin-bottom:1em;
+ border:solid 1px;
+}
DIV.page {
background-color:white;
margin-left:0.25in;
1.2 +1 -1 newsite/documentation/JMX.Connector.Howto.html
Index: JMX.Connector.Howto.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/documentation/JMX.Connector.Howto.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- JMX.Connector.Howto.html 2000/11/12 20:33:24 1.1
+++ JMX.Connector.Howto.html 2001/01/19 09:18:04 1.2
@@ -224,7 +224,7 @@
</LI>
</OL>
</DIV>
-<H3>How to create a client without the server and protocol/H3>
+<H3>How to create a client without the server and protocol</H3>
<DIV class="para" ALIGN="left">
First you have to make sure that the JNDI property: <B>java.naming.provider.url</B>
points to the JNDI server your JMX Connectors are registered to. At the moment
1.3 +12 -11 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.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- JMX.ExternalContext.HowTo.html 2001/01/17 03:43:36 1.2
+++ JMX.ExternalContext.HowTo.html 2001/01/19 09:18:04 1.3
@@ -75,7 +75,7 @@
is designed to only work within a single VM. Future versions of the ExternalContext
mbean will provide support for enabling remote access to the federated context if
desired.
-
+</div>
<h2>Preparation of the JNDIView MBean</h2>
<div class="para" align="left">
All that is required to use the JNDIView service is to add it to jboss.jcml
@@ -83,6 +83,7 @@
<pre class="code" align="left">
<mbean code="org.jboss.naming.JNDIView" name="DefaultDomain:service=JNDIView"
>
</mbean>
+</pre>
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>
@@ -94,7 +95,7 @@
<a href="http://localhost:8082/">http://localhost:8082/</a>. On this page you will
see a section that lists the registered MBeans by domain. It should look something
like this:
- <div class="page">
+ <span class="page">
<HR>
<H4>List of registered MBeans by domain:</H4>
<UL class="none" type=circle style="background-color: white">
@@ -114,32 +115,32 @@
<LI><em>...</em>
</ul>
</UL>
- </div>
+ </span>
This is showing two registered ExternalContext mbeans(ExternalContext/FS[a
filesystem] and
ExternalContext/LDAP[an ldap server]) mbeans as well as the JNDIView mbean.
Selecting the
service=JNDIView link takes you to the JNDIView MBean View which will have a list
of MBean operations section similar to:
- <div class="page">
+ <span class="page">
<HR>
<P><H3> List of MBean operations:</H3>
- <HR><B style="background-color:white">Description of list</B></A>
+ <HR><B style="background-color:white">Description of list</B>
<FORM METHOD=GET>
<TABLE>
<TR><TD>java.lang.String</TD>
<TD><INPUT TYPE=SUBMIT NAME="action" VALUE="list"></TD>
<TD>(boolean)param0</TD>
<TD><INPUT TYPE=RADIO NAME="param0+boolean" CHECKED VALUE="true">True <INPUT
TYPE=RADIO NAME="param0+boolean" VALUE="false">False </TD>
- </TR><TR><TD></TD>
</TR></TABLE>
</FORM>
- <HR><B style="background-color:white">Description of destroy</B></A>
- <p>...
- </div>
+ <HR><B style="background-color:white">Description of destroy</B>
+ <p>...</p>
+ </span>
+
Invoking the list operation creates a dump of the JBoss JNDI namespace that includes
the federated external contexts. As an example, this is the dump with the filesystem
and ldap contexts:
- <div class="page">
+ <span class="page">
<HR><P>
<FONT SIZE=+3 COLOR=green><B style="background-color:white">list
Successful</B></FONT><P><HR><P>The operation [list] was successfully invoked for the
MBean [DefaultDomain:service=JNDIView].<BR>The operation returned with the value:<P>
<pre> +- RMITopicConnectionFactory (class: org.spydermq.SpyTopicConnectionFactory)
@@ -239,7 +240,7 @@
</pre>
</div>
-</div>
+</span>
<div class="footer" align="left">
If you comments/questions/problems, you can ask them on the jboss-user mail
1.2 +1 -0 newsite/documentation/JMX.Timer.HowTo.html
Index: JMX.Timer.HowTo.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/documentation/JMX.Timer.HowTo.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- JMX.Timer.HowTo.html 2000/12/08 05:33:19 1.1
+++ JMX.Timer.HowTo.html 2001/01/19 09:18:04 1.2
@@ -86,6 +86,7 @@
2000. Then you connect to a MBeanServer through the JMXConnector interface
which is more or less the same.
</LI>
+</ul>
</DIV>
<DIV class="para" ALIGN="left">
We are nearly there: now we need the reference to the timer service to work on
1.2 +3 -3 newsite/documentation/ejb.html
Index: ejb.html
===================================================================
RCS file: /products/cvs/ejboss/newsite/documentation/ejb.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ejb.html 2000/11/12 20:33:26 1.1
+++ ejb.html 2001/01/19 09:18:04 1.2
@@ -18,11 +18,11 @@
<p>jBoss uses XML to add deployment information that is specific to
jBoss, such as which plugins to use, which JNDI-names to bind the homes to, etc. The
configuration must be located in the file META-INF/jboss.xml, next to the ejb-jar.xml
file containing the EJB 1.1 XML descriptor file. This file could be edited manually,
but it is recommended that it is done through the EJX XML editor. The EJX editor is
bundled with jBoss, and can be started by executing the /bin/ejx.jar executable
JAR-file. EJX is a generic XML editor framework, which supports plugins for specific
XML types. jBoss provides two plugins for EJX. These are located in the
/lib/ext/ejxjboss.jar and /lib/ext/ejxjaws.jar files, and are used automatically by
EJX, since EJX scans the /lib/ext directory for plugins.</p>
<p>Once you have created the EJB 1.1 XML descriptor for your beans,
either by manual editing of the ejb-jar.xml file, or by using the EJB 1.1 support
provided in the EJX editor, it is time to add the jBoss specific configuration
information. This is done by opening the ejb-jar.xml file as a jBoss configuration
file. This will load the information in ejb-jar.xml, and also construct a GUI where
additional settings may be made. These additional settings will be stored in jboss.xml
when you select Save in the GUI.</p>
<p>There are two main categories of information in the jBoss XML file:
container configurations and bean configurations. A container configuration is a
selection of plugins, and settings for those plugins. For example, you may choose to
make a configuration for EntityBeans that uses a particular instance cache that suits
your needs, and a persistence manager that supports your backing store. These plugins
may then be configured to behave in a certain way. Once you have created a
configuration one or more beans may be configured to use this configuration. This
allows you to have one configuration for all beans (i.e. one size fits all), or one
configuration for each bean. Both options are possible. A couple of default
configurations are loaded automatically when you create a new jBoss descriptor. Below
is a screenshot showing a container configuration being constructed.</p>
- <p><img src="picture/confgui.gif">
+ <p><img src="../pictures/confgui.gif">
<p>Besides container configurations you may also add information that
is specific for each bean, such as which JNDI-name to bind a bean to. Below is a
screenshot showing a bean being configured.</p>
- <p><img src="picture/jbossgui.gif">
+ <p><img src="../pictures/jbossgui.gif">
<p>If any of your beans use the JAWS CMP plugin, you should repeat the
above but instead select JAWS when opening the ejb-jar.xml file. This will allow you
to set the database settings for your CMP beans. Below is a screenshot of the JAWS GUI
plugin.</p>
- <p><img src="picture/jawsgui.gif">
+ <p><img src="../pictures/jawsgui.gif">
<h3>Deploying your beans</h3>
<p>Once you have configured your beans, you may deploy them. You can
do this manually, or automatically. The manual way is to use some management console
to invoke the container factory to deploy the EJB-JAR. You can deploy your beans
automatically by using the AutoDeployer component. The AutoDeployer component can be
set to watch the modification timestamp of an individual EJB-JAR, or watch the
contents of a given directory. In the latter case, if a valid EJB-JAR is added to the
directory it will be automatically deployed into the server. Any updates to the JAR
will result in a re-deployment. When a re-deployment is made the currently constructed
containers are first stopped and undeployed, and the new JAR is then deployed. Any
changed classes will be reloaded if they have been loaded by the container
classloader. Any helper classes loaded by the server classloader will, of course, not
be reloaded.</p>
<p>For development purposes you may also place a directory in the
directory that is watched by the AutoDeployer. If its structure is the same as that of
a valid EJB-JAR (i.e. it contains a META-INF sub-directory with deployment
descriptors) it will get deployed in the server. Instead of watching the timestamp of
the directory the AutoDeployer watches the timestamp of the META-INF/ejb-jar.xml file.
This is very useful during development as you can code and recompile your beans, and
then redeploy them as many times as you want by simple opening the ejb-jar.xml file in
an editor and storing it again.
