User: luke_t
Date: 01/11/29 18:50:06
Modified: src/xdocs faq.xml
Log:
more faq filling ...
Revision Changes Path
3.1 +162 -89 manual/src/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/xdocs/faq.xml,v
retrieving revision 3.0
retrieving revision 3.1
diff -u -r3.0 -r3.1
--- faq.xml 2001/11/18 20:10:57 3.0
+++ faq.xml 2001/11/30 02:50:06 3.1
@@ -6,11 +6,11 @@
<articleinfo>
<title>JBoss FAQ</title>
- <releaseinfo>$Revision: 3.0 $, $Date: 2001/11/18 20:10:57 $</releaseinfo>
+ <releaseinfo>$Revision: 3.1 $, $Date: 2001/11/30 02:50:06 $</releaseinfo>
<!--revhistory>
<revision>
- <revnumber>$Revision: 3.0 $</revnumber>
- <date>$Date: 2001/11/18 20:10:57 $</date>
+ <revnumber>$Revision: 3.1 $</revnumber>
+ <date>$Date: 2001/11/30 02:50:06 $</date>
</revision>
</revhistory>
-->
@@ -33,7 +33,7 @@
<qandaentry id="faq.intro.version">
<question><para>What is the version of this FAQ and when was it last
updated?</para></question>
<answer>
- <para>This is $Revision: 3.0 $ of the FAQ. The last update was made
on $Date: 2001/11/18 20:10:57 $.</para>
+ <para>This is $Revision: 3.1 $ of the FAQ. The last update was made
on $Date: 2001/11/30 02:50:06 $.</para>
</answer>
</qandaentry>
@@ -41,26 +41,28 @@
<question><para>Who is responsible for this FAQ?</para></question>
<answer>
<para>Everybody :).</para>
- <para>TODO: list original creators and maintainers...</para>
- <!--
- The first version of the JBoss FAQ was created by Kunle Odutola in
March 2000. The second version of the FAQ was a rewrite by Jeremiah Johnson in August
2000 with maintenance by Kunle Odutola. The current version is maintained by Dewayne
McNair.
-
- Most of the wisdom contained in the answers presented here however
comes from the collective insights and diligence of the many others who inhabit the
JBoss mailing list(s) and the EJB world-at-large.
-
- -->
+ <para>The original JBoss FAQ was created by Kunle Odutola in March
2000. The second version of the FAQ was a rewrite by Jeremiah Johnson in August 2000
with maintenance by Kunle Odutola. Maintenance subsequently passed on to Dewayne
McNair... The current version has been <ulink
url="http://www.docbook.org";>docbookified</ulink> and will be maintained as part of
the <ulink url="http://www.jboss.org/online-manual/HTML/";>online manual</ulink>.
+ </para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Where can I get the latest version of this
FAQ?</para></question>
<answer>
- <para>This incarnation of the JBoss FAQ is intended to provide a
more comprehensive set of entry points into the online manual as well as being a
single, condensed source of information on JBoss. As such, it can be found along with
the manual on the <ulink url="http://www.jboss.org";>JBoss website.</ulink></para> <!--
TODO: more exact link -->
+ <para>This incarnation of the JBoss FAQ is intended to provide a
more comprehensive set of entry points into the online manual as well as being a
single, condensed source of information on JBoss. As such, it can be found along with
the manual on the <ulink url="http://www.jboss.org/online-manual/HTML/";>JBoss
website.</ulink></para>
</answer>
</qandaentry>
+ <qandaentry>
+ <question><para>What other documentation is available apart from this
FAQ?</para></question>
+ <answer>
+ <para>You can browse the <ulink
url="http://www.jboss.org/online-manual/HTML/";>online manual</ulink>. However this is
not intended as an in-depth source of information, but rather to get you up and
running.</para>
+ <para>You are encouraged to purchase the full <ulink
url="http://www.jboss.org/doco.jsp";>documentation</ulink> which is up to date, written
by the developers and is available at minimal cost. This also supports future
development.</para>
+ </answer>
+ </qandaentry>
</qandadiv>
-
+<!-- General J2EE -->
<qandadiv id="faq.general">
<title>General</title>
<para>Basic questions about J2EE.</para>
@@ -168,8 +170,22 @@
</answer>
</qandaentry>
+ <qandaentry>
+ <question><para>What else should I take a look at if I want more
in-depth general information?</para></question>
+ <answer>
+ <itemizedlist>
+ <listitem>
+ <para>The <ulink
url="http://java.sun.com/j2ee/j2ee-1_3-fr-spec.pdf";>J2EE Specification</ulink>.</para>
+ </listitem>
+ </itemizedlist>
+
+ </answer>
+ </qandaentry>
+
</qandadiv>
+<!-- End of General J2EE -->
+<!-- General JBoss -->
<qandadiv>
<title>JBoss</title>
<para>General questions on JBoss, licensing, business/commercial benfits,
support, training and supported features.</para>
@@ -195,7 +211,7 @@
<answer>
<para>JBoss is an open source project. It came into existence due
entirely to the generosity of a small but growing group of very talented and prolific
software developers and architects who designed, developed and continue to improve the
suite of J2EE application servers. The project has survived up to this point because
this group has remained dedicated and invested significant resources into the project.
As a result the project has thrived and an equally dedicated community of users
continue to grow around it at a phenomenal rate.
</para>
- <para>JBoss is now a large and successful open source project with
the binary distributions being downloaded thousands of times per day (72,000 downloads
per month as of October 2001). A project of this size only survives because
<emphasis>everyone</emphasis> in the project's community actively contribute to it's
future. There are many forms of contributions including financial or equipment
donations, technical skills in software development and testing and, insightful wisdom
and real-life feedback as technical authors and documenters. <emphasis>What are you
going to contribute?</emphasis>
+ <para>JBoss is now a large and successful open source project with
the binary distributions being downloaded thousands of times per day (72,000 downloads
per month as of October 2001). A project of this size only survives because
<emphasis>everyone</emphasis> in the project's community actively contribute to it's
future.
</para>
</answer>
</qandaentry>
@@ -205,7 +221,7 @@
<answer>
<para>No. In fact, in many ways, you are less at risk. JBoss is now
a stable and robust product which has matured over a period of several years. There
are now lots of people using JBoss, many commercial users and a high number of
experienced and committed developers - the openness of the project means it has been
widely exposed to peer review and there is high-quality <link
linkend="faq.jboss.support">support</link> available. The JMX-based design is highly
flexible and pluggable - if needed, you can customize JBoss to fit your requirements.
In contrast, the closed-source nature of most commercial servers means the
implementation is to a large extent hidden from application developers. This
"black-box" effect can be very frustrating when things go wrong - you then have very
limited options when it comes to working out what is going on <quote>inside</quote>
the server.</para>
- <para>The extremely high deployment cost of many commercial J2EE
servers is also a serious consideration. The saving you make in license fees by using
JBoss (potentially thousands of dollars) can be invested in your hardware budget
instead.</para> <!--TODO: link to recent article on total cost (more money for
hardware). -->
+ <para>The extremely high deployment cost of many commercial J2EE
servers is also a serious consideration. The saving you make in license fees by using
JBoss (potentially thousands of dollars) can be invested in your hardware budget
instead. See for example the following post on <ulink
url="http://www.theserverside.com/home/thread.jsp?thread_id=8632#28251";>theserverside.com</ulink></para>.
<para>If you still have doubts, or there is pressure from elsewhere
to use a particular commercial server, then why not try developing for JBoss in
parallel? This will keep your deployment options open and you can make a direct
comparison for yourself before making any firm commitments either way.</para>
</answer>
@@ -231,14 +247,14 @@
<qandaentry id="faq.jboss.compliance">
<question><para>How compliant is JBoss with the J2EE specs? I've heard
that it hasn't been certified by Sun.</para></question>
<answer>
- <para>JBoss is committed to providing an implementation that is
fully compliant with the J2EE spec. Certification is prohibitively expensive for an
open source project.</para>
+ <para>JBoss is committed to providing an implementation that is
fully compliant with the J2EE spec. At the moment, certification is prohibitively
expensive for an open source project like JBoss. You can read more about this on
<ulink url="http://www.jboss.org/licensesun.jsp";>jboss.org</ulink>.</para>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.versions">
<question><para>What versions are available, and where can I get
them?</para></question>
<answer>
- <para>The two main versions of JBoss which are currently releveant
are the stable 2.4 branch and the next generation "Rabbit Hole" release 3.0 which
should appear in alpha soon. The various binary releases can be obtained from <ulink
url="http://sourceforge.net/projects/jboss/";>Sourceforge</ulink>.
+ <para>The two main versions of JBoss which are currently releveant
are the stable 2.4 branch and the next generation "Rabbit Hole" release 3.0 which is
currently (November 2001) in alpha release. The various binary releases can be
obtained from <ulink url="http://sourceforge.net/projects/jboss/";>Sourceforge</ulink>.
</para>
</answer>
</qandaentry>
@@ -260,7 +276,7 @@
<qandaentry id="faq.jboss.cluster">
<question><para>Does JBoss support clustering and transparent
failover?</para></question>
<answer>
- <para>Clustering is being implemented in JBoss 3 through the JBossHA
(<quote>High Availability</quote>) module. It is based on the <ulink
url="http://www.javagroups.org";>JavaGroups</ulink> framework. See the <link
linkend="clustering">clustering chapter</link> for more information.</para>
+ <para>Clustering is being implemented in JBoss 3 through the JBossHA
(<quote>High Availability</quote>) module. It is based on the <ulink
url="http://www.javagroups.com";>JavaGroups</ulink> group communication toolkit. See
the <link linkend="clustering">clustering chapter</link> for more information.</para>
</answer>
</qandaentry>
@@ -276,7 +292,7 @@
<question><para>Can I sell JBoss?</para></question>
<answer>
<para>Yes, and many do. Many bundle it with J2EE applications for
example.</para>
- <para>If you want to sell <emphasis>only</emphasis> JBoss, then you
need to ask <quote>what is the value added?</quote> Just putting it on a CD and
selling may not get you many customers if they can download it from the net just as
easy.</para>
+<!-- this seems a bit crap. L.T. <para>If you want to sell
<emphasis>only</emphasis> JBoss, then you need to ask <quote>what is the value
added?</quote> Just putting it on a CD and selling may not get you many customers if
they can download it from the net just as easy.</para> -->
</answer>
</qandaentry>
@@ -322,6 +338,7 @@
</answer>
</qandaentry>
</qandadiv>
+ <!-- End of General JBoss -->
<!-- Admin -->
@@ -329,6 +346,21 @@
<title>Server Admin and Configuration</title>
<para>Installation, starting, stopping. Where to find the basic server
configuration files, what they contain. Monitoring and instrumentation services
etc.</para>
+<!-- FIXME: need to differentiate strongly between JBoss 2.* and JBoss 3.0 here -->
+ <qandaentry>
+ <question><para>Where are the JBoss configuration files
stored?</para></question>
+ <answer>
+ <para>The <quote>default</quote> configuration files are stored in
<filename>conf/default</filename>. You can create your own additional setups by making
a copy of this directory and passing the name argument to the server on startup. More
information on the configuration files can be found in the <link
linkend="configuration">manual.</link> The most important configuration file is
<filename>jboss.jcml</filename> which is where you are most likely to want to make
changes.</para>
+ </answer>
+ </qandaentry>
+
+ <qandaentry id="faq.admin.tools">
+ <question><para>What options or tools are available for administering
and monitoring a running JBoss server?</para></question>
+ <answer>
+ <para>JMX. Intended support for JSR77 etc.</para>
+ </answer>
+ </qandaentry>
+
<qandaentry id="faq.admin.shutdown">
<question><para>How do I cleanly shutdown JBoss?</para></question>
<answer>
@@ -338,6 +370,14 @@
</qandaentry>
<qandaentry>
+ <question><para>I heard that I can't use the JMX Web management
interface in a commercial deployment, is this true?</para></question>
+ <answer>
+ <para>Yes. Sun licensing issues forbid its commenrcial use.</para>
+ </answer>
+ </qandaentry>
+
+<!-- FIXME is this still relevant/correct -->
+ <qandaentry>
<question><para>Why won't JBoss run when installed in a path with
spaces?</para></question>
<answer>
<para>Due to a SUN feature (the implementation of URL + the RMI
classloader) JBoss may experience errors when it is run from a path that contains a
space in it. There is a feature in JBoss that you can enable that will cope with this
problem. To enable it, add the following MBean configuration section to the top of
jboss.jcml :
@@ -350,6 +390,13 @@
</answer>
</qandaentry>
+ <qandaentry id="faq.admin.bootstart">
+ <question><para>How do I configure JBoss to start when the server
boots ?</para></question>
+ <answer>
+ <para><!-- FIXME pull script from jboss-user archives and try it out
-->For Windows NT see <xref linkend="faq.admin.ntservice"/>. <!-- FIXME: this script
isn't there anymore - For Unix based systems look at the jboss_init_redhat.sh script
in the dist/bin directory. This is fairly configurable, allowing you to start and stop
jboss and can be used from the system boot scripts -->. For Unix based systems, see
the following message from the mail archives: <ulink
url="http://www.mail-archive.com/[email protected]/msg10908.html";>Starting
JBoss as a service on Linux</ulink></para>
+ </answer>
+ </qandaentry>
+
<qandaentry id="faq.admin.ntservice">
<question><para>How do I run JBoss as a service on Windows
NT</para></question>
<answer>
@@ -361,27 +408,6 @@
</answer>
</qandaentry>
- <qandaentry>
- <question><para>What files are used for server
configuration?</para></question>
- <answer>
- <para>answer.</para>
- </answer>
- </qandaentry>
-
- <qandaentry id="faq.admin.tools">
- <question><para>What options or tools are available for administering
and monitoring a running JBoss server?</para></question>
- <answer>
- <para>JMX. Intended support for JSR77 etc.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question><para>I heard that I can't use the JMX Web interface in a
commercial deployment, is this true?</para></question>
- <answer>
- <para>Yes. Sun licensing issues forbid its commenrcial use.</para>
- </answer>
- </qandaentry>
-
</qandadiv>
<qandadiv id="faq.ejb">
@@ -448,7 +474,7 @@
<qandaentry>
<question><para>Question.</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
@@ -456,7 +482,7 @@
<!-- End of EJB section -->
-
+ <!-- CMP stuff -->
<qandadiv>
<title>Container-Managed Persistence (CMP)</title>
<para>CMP implementations, spec versions etc.</para>
@@ -464,7 +490,8 @@
<qandaentry>
<question><para>What is CMP and how do I use it with
JBoss?</para></question>
<answer>
- <para>Default impl - link to manual.</para>
+ <para>...</para>
+
</answer>
</qandaentry>
@@ -472,13 +499,14 @@
<question><para>Does JBoss support the CMP features from EJB
2.0?</para></question>
<answer>
<para>Support for EJB 2.0 CMP is a central feature for JBoss
3.0</para>
+ <para>You can purchase <ulink
url="http://www.flashline.com/Components/View.jsp?prodid=4312";>full
documentation</ulink> for the CMP 2.0 engine, written by the author.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>What alternatives are there to the default
implementation?</para></question>
<answer>
- <para>Integration with other persistence engines, Cocobase, write
your own persistence layer? </para>
+ <para>... <!-- Integration with other persistence engines, Cocobase,
write your own persistence layer?--> </para>
</answer>
</qandaentry>
@@ -504,10 +532,75 @@
</qandaentry>
</qandadiv>
+ <!-- End of CMP stuff -->
+ <!-- Database stuff -->
+ <qandadiv id="faq.resource">
+ <title>Databases and Other Enterprise Resources.</title>
+ <para>Most of this material is linked to the corresponding chapter of the
<link linkend="resource">manual</link>.</para>
- <!-- Web container stuff -->
+ <qandaentry id="faq.resource.newbie">
+ <question><para>I'm new to this stuff and I don't even know what a
DataSource is.</para></question>
+ <answer>
+ <para>A <ulink
url="http://java.sun.com/j2se/1.4/docs/api/javax/sql/DataSource.html";>DataSource</ulink>
is the preferred Java abstraction for obtaining database connections. You will
usually set up datasources as part of your server configuration along with a name
under which it will be bound in the server's JNDI implementation. The DataSource
usually also hides the implementation of connection pooling from the client.</para>
<!-- link to BMP example? -->
+ </answer>
+ </qandaentry>
+
+ <qandaentry>
+ <question><para>How do I set up a database connection
pool?</para></question>
+ <answer>
+ <para>You should configure a DataSource for the database you want to
use. For JBoss 2.4.* see <xref linkend="faq.resource.ds24"/>. For JBoss 3.* see <xref
linkend="faq.resource.ds3"/></para>
+ </answer>
+ </qandaentry>
+ <qandaentry id="faq.resource.ds24">
+ <question><para>How do I set up a Datasource in JBoss
2.4.*?</para></question>
+ <answer>
+ <para>In JBoss 2.4.* you add an entry to the JDBC section in
<filename>jboss.jcml</filename>. You can use the any existing ones as a template. You
should also add your driver to the comma-separated list of drivers at the top of the
JDBC section. For example if you wanted set up a datasource with a SQL server
database, using Weblogic's drivers, you would have something like:
+ <programlisting><![CDATA[
+ <!-- ==================================================================== -->
+ <!-- JDBC -->
+ <!-- ==================================================================== -->
+
+ <mbean code="org.jboss.jdbc.JdbcProvider"
name="DefaultDomain:service=JdbcProvider">
+ <attribute name="Drivers">weblogic.jdbc.mssqlserver4.Driver</attribute>
+ </mbean>
+
+ <mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=SQLSRVRDS">
+ <attribute name="PoolName">SQRSRVRDS</attribute>
+ <attribute
name="DataSourceClass">org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl</attribute>
+ <attribute
name="URL">jdbc:weblogic:mssqlserver4:YOUR_DB_NAME@YOUR_DB_SERVER:1433</attribute>
+ <attribute name="JDBCUser">sa</attribute>
+ <attribute name="Password">password</attribute>
+ <attribute name="MinSize">1</attribute>
+ <attribute name="MaxSize">10</attribute>
+ </mbean>
+ ]]>
+ </programlisting>
+Where you would substitute your own chosen name for the attribute "PoolName". This
will be the name under which the Datasource is bound into JNDI. Obviously you would
also modify the URL appropriately and select a username and password for your
database, and you might mant to modify the pool size here. There are other attributes
which can be set here, but you can probably forget about most of them to start with.
+ </para>
+ </answer>
+ </qandaentry>
+
+ <qandaentry id="faq.resource.ds3">
+ <question><para>How do I set up a Datasource in JBoss
3.*?</para></question>
+ <answer>
+ <para>In JBoss 3, database access uses the Java Connector
Architecture (<ulink url="http://java.sun.com/j2ee/connector/";>JCE</ulink>)which
provides a standard mechanism for accessing enterprise resources (not just databases)
from a J2EE server. It uses the concept of a <quote>Resource Adaptor</quote> to manage
connections, transactions and security between the app. server and the external
resource.</para>
+ <para>You can read more about this, along with examples for specific
databases in the <link linkend="resource-intro">manual</link>.</para>
+ </answer>
+ </qandaentry>
+
+ <qandaentry>
+ <question><para>How do I configure Database X to work with
JBoss?</para></question>
+ <answer>
+ <para>...</para>
+ </answer>
+ </qandaentry>
+
+ </qandadiv>
+ <!-- End of Database stuff -->
+
+ <!-- Web container stuff -->
<qandadiv id="faq.web">
<title>Web Applications</title>
<para>Integration with web containers, apache, tomcat, jetty etc.
Configuring web apps, jboss-web.xml</para>
@@ -527,75 +620,59 @@
</qandaentry>
<qandaentry id="faq.web.security">
- <question><para>How does security work with the integrated web
containers?</para></question>
+ <question><para>How does security work between web containers and
JBoss?</para></question>
<answer>
- <para>Integration with JBoss security. Link to security section and
manual. Stress downloading of pre-configured bundles.</para>
+ <para>It depends largely on whether you are using one of the
integrated bundles or a web container in a separate VM. In the latter case, the web
container is no different to any other JBoss client - its own authentication and
access controls must be configured independently of JBoss.</para>
+ <para>Your best bet, at least initially, is to use one of the
bundled JBoss/Jetty or JBoss/Tomcat packages. These are pre-configured with integrated
security.</para>
</answer>
</qandaentry>
<qandaentry id="faq.web.jbosswebfile">
<question><para>What is <filename>jboss-web.xml</filename>
for?</para></question>
<answer>
- <para>...</para>
+ <para><filename>jboss-web.xml</filename> is where you set the
vendor-specific information (i.e. JBoss-specific) information for your web
application. It allows you to specify a security domain and set up JNDI bindings. The
relevant section of the manual is <xref linkend="web-container.config"/></para>
</answer>
</qandaentry>
</qandadiv>
-
<!-- End of Web container stuff -->
-
- <!-- Database stuff -->
- <qandadiv>
- <title>Databases</title>
- <para>Is a separate section on DBs needed? Probably. How to use Oracle XA
impl etc.</para>
- <qandaentry>
- <question><para>Question.</para></question>
- <answer>
- <para>This is the answer.</para>
- </answer>
- </qandaentry>
-
+ <!-- Security -->
+ <qandadiv id="faq.security">
+ <title>Security</title>
+ <para>Security in JBoss, JBossSX, JAAS, Web integration, security proxies
etc.</para>
<qandaentry>
- <question><para>Question.</para></question>
+ <question><para>What is JBossSX?</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
- </qandadiv>
-
- <!-- End of Database stuff -->
-
- <!-- Security -->
- <qandadiv>
- <title>Security</title>
- <para>Security in JBoss, JBossSX, JAAS, Web integration, security proxies
etc.</para>
<qandaentry>
- <question><para>Question.</para></question>
+ <question><para>What is JAAS and what does it have to do with
JBoss?</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
<qandaentry>
- <question><para>Question.</para></question>
+ <question><para>Blank Question.</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
<qandaentry>
- <question><para>Question.</para></question>
+ <question><para>Blank Question.</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
<qandaentry>
- <question><para>Question.</para></question>
+ <question><para>Blank Question.</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
@@ -605,31 +682,27 @@
<qandadiv>
<title>JBoss Architecture and Development.</title>
<para>Advanced questions on the internal architecture of JBoss. JBoss
development, test suite etc.</para>
- <qandaentry>
- <question><para>Question.</para></question>
- <answer>
- <para>This is the answer.</para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question><para>Question.</para></question>
+ <qandaentry id="faq.arch.build">
+ <question><para>How do I build JBoss from the sourcecode in
CVS?</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>First read the CVS information on <ulink
url="http://www.jboss.org/developers/cvs.jsp";>jboss.org</ulink>. To build JBoss you
want to checkout the <varname>jboss-all</varname> module. Then change directory to
<filename>jboss-all/build</filename> and type "build" for Windows or "sh build.sh" if
you're using unix, linux or cygwin. The build should produce a working JBoss server
distribution in <filename>jboss-all/build/output</filename>.
+ </para>
+ <para>You can also run the command "build help" for a list of
available build targets.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>...</para>
</answer>
</qandaentry>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
