User: luke_t
Date: 01/11/16 17:28:10
Modified: src/xdocs faq.xml
Log:
more basic knocking into shape
Revision Changes Path
1.2 +69 -51 manual/src/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /cvsroot/jboss/manual/src/xdocs/faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq.xml 2001/11/15 22:03:59 1.1
+++ faq.xml 2001/11/17 01:28:10 1.2
@@ -1,15 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- !DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"docbookx/docbookx.dtd" -->
+<!-- DOCTYPE article SYSTEM "../../../ThirdParty/oasis/docbook-xml/docbookx.dtd" -->
+
<article class="faq">
<articleinfo>
<title>JBoss FAQ</title>
- <releaseinfo>$Revision: 1.1 $, $Date: 2001/11/15 22:03:59 $</releaseinfo>
+ <releaseinfo>$Revision: 1.2 $, $Date: 2001/11/17 01:28:10 $</releaseinfo>
<!--revhistory>
<revision>
- <revnumber>$Revision: 1.1 $</revnumber>
- <date>$Date: 2001/11/15 22:03:59 $</date>
+ <revnumber>$Revision: 1.2 $</revnumber>
+ <date>$Date: 2001/11/17 01:28:10 $</date>
</revision>
</revhistory>
-->
@@ -32,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: 1.1 $ of the FAQ. The last update was made
on $Date: 2001/11/15 22:03:59 $.</para>
+ <para>This is $Revision: 1.2 $ of the FAQ. The last update was made
on $Date: 2001/11/17 01:28:10 $.</para>
</answer>
</qandaentry>
@@ -41,12 +42,12 @@
<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.
+ <!--
+ 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.
+ 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.
--->
+ -->
</answer>
</qandaentry>
@@ -70,26 +71,23 @@
The Java 2 Platform Enterprise Edition (J2EE) is the platform
for developing, deploying and managing n-tiered information systems using Java
technologies. The platform encourages the development of enterprise systems with the
ability to run <emphasis>anywhere</emphasis> across a wide range of operating systems.
J2EE extends the Java 2 Platform to cater for the server-side processing needs of the
enterprise with key technologies including the following:
<itemizedlist>
- <!-- TODO: Add links to java.sun.com etc. here -->
- <listitem><para>Enterprise JavaBeans (EJB)</para></listitem>
-
- <listitem><para>Java Naming and Directory Interface
(JNDI)</para></listitem>
+ <listitem><para>Enterprise JavaBeans (<ulink
url="http://java.sun.com/products/ejb/index.html";>EJB</ulink>)</para></listitem>
- <listitem><para>JDBC data access API</para></listitem>
+ <listitem><para>Java Naming and Directory Interface (<ulink
url="http://java.sun.com/products/jndi/index.html";>JNDI</ulink>)</para></listitem>
- <listitem><para>Java Servlets</para></listitem>
+ <listitem><para><ulink
url="http://java.sun.com/products/jdbc/index.html";>JDBC</ulink> data access
API</para></listitem>
- <listitem><para>JavaServer Pages (JSP)</para></listitem>
+ <listitem><para>Java <ulink
url="http://java.sun.com/products/servlet/index.html";>Servlets</ulink></para></listitem>
- <listitem><para>Java Transaction API (JTA)</para></listitem>
+ <listitem><para>JavaServer Pages (<ulink
url="http://java.sun.com/products/jsp/index.html";>JSP</ulink>)</para></listitem>
- <listitem><para>Java Transaction Service
(JTS)</para></listitem>
+ <listitem><para>Java Transaction API (<ulink
url="http://java.sun.com/products/jta/index.html";>JTA</ulink>)</para></listitem>
- <listitem><para>Java Messaging Service
(JMS)</para></listitem>
+ <listitem><para>Java Transaction Service (<ulink
url="http://java.sun.com/products/jts/index.html";>JTS</ulink>)</para></listitem>
+ <listitem><para>Java Messaging Service (<ulink
url="http://java.sun.com/products/jms/index.html";>JMS</ulink>)</para></listitem>
+ <listitem><para>Remote Method Invocation (<ulink
url="http://java.sun.com/products/jdk/rmi/index.html";>RMI</ulink>)</para></listitem>
- <listitem><para>Remote Method Invocation
(RMI)</para></listitem>
-
- <listitem><para>CORBA</para></listitem>
+ <listitem><para><ulink
url="http://www.corba.org";>CORBA</ulink></para></listitem>
</itemizedlist>
Further information about Java 2 Platform Enterprise Edition
(J2EE) is available on the <ulink url="http://java.sun.com/j2ee/";>J2EE home
page.</ulink>
@@ -165,7 +163,8 @@
<qandaentry id="faq.general.jmx">
<question><para>What are these MBeans and JMX that I keep hearing
about?</para></question>
<answer>
- <para>...</para>
+ <para><quote>Managed Beans</quote> are part of the Java Management
Extensions Specification<ulink
url="http://java.sun.com/products/JavaManagement/";>(JMX)</ulink> (formerly JMAPI).
This provides an architecture and API for application management using Java. JBoss has
made JMX its own and it forms the basis of the entire JBoss infrastructure. JBoss is
basically a series of MBean service components plugged together using JMX as the bus.
See the <link linkend="design.jmx">design notes</link> for more information.</para>
+ <para>For an in-depth explanation of JMX and its potential uses, see
the forthcoming book by Juha Lindfors FIXME ref, date.</para>
</answer>
</qandaentry>
@@ -186,7 +185,7 @@
<qandaentry id="faq.jboss.jbossgroup">
<question><para>What is the JBoss Group?</para></question>
<answer>
- <para>answer....TODO: blah, commercial arm etc. More on
jboss.org</para>
+ <para>JBoss Group is the commercial arm of JBoss which complements
the free, open source offering by selling training, support, consulting and
documentation. You can find out more on the <ulink url="http://www.jboss.org";>web
site.</ulink></para>
</answer>
</qandaentry>
@@ -204,25 +203,25 @@
<qandaentry id="faq.jboss.vscommercial">
<question><para>Isn't it more risky than using a commercial app
server?</para></question>
<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 available</link>. 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>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. TODO: link to recent article on total cost
(more money for hardware).</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>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>
</qandaentry>
<qandaentry id="faq.jboss.refsites">
- <question><para>OK, so who's using it in practice?</para></question>
+ <question><para>OK. So who's using it in practice?</para></question>
<answer>
- <para>TODO: Link to jboss.org ref sites list.</para>
+ <para>There is a set of testimonials on the <ulink
url="http://www.jboss.org/testimonials.jsp";>JBoss web site</ulink>.</para>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.support">
<question><para>What support is available? Won't the support be better
from a commercial vendor?</para></question>
<answer>
- <para>Support is provided through the online forums and newsgroups
(TODO nntp availability?, add links). The open source nature of JBoss means there are
a lot of people participating in the lists who have knowledge of the server internals.
Most of the people who develop the JBoss code are also active on the lists so the
support is generally of a high quality.</para>
+ <para>Support is provided through the online <ulink
url="http://www.jboss.org/forums/index.jsp";>forums</ulink> and newsgroups (TODO nntp
availability?). The open source nature of JBoss means there are a lot of people
participating in the lists who have knowledge of the server internals. Most of the
people who develop the JBoss code are also active on the lists so the support is
generally of a high quality.</para>
<para>Any problems or bugs in the code are well publicised and
openly discussed, so you will usually be aware of them. This is not always the case
with commercial vendors who are often keen to avoid acknowledging bugs for fear of bad
publicity.</para>
<para>There is also a development mailing list intended for
discussing issues related to the development of JBoss itself. You shouldn't post user
questions here, but there are some interesting discussions if you want to get a more
in-depth knowledge of application server development. </para>
<para>If you feel you need a paid support contract, then you can
obtain one from the <ulink url="http://www.jboss.org";>JBoss Group.</ulink></para>
@@ -232,14 +231,15 @@
<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>answer....from jboss.org</para>
+ <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>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.versions">
<question><para>What versions are available, and where can I get
them?</para></question>
<answer>
- <para>answer.... SF link. refer to JBoss 2.4 and 3.0 RH. </para>
+ <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>
</answer>
</qandaentry>
@@ -248,15 +248,19 @@
<answer>
<para>Choosing performance and scalability metrics for comparing
application servers is a difficult business and many comparison tests are
unconvincing. The performance of a realistic J2EE test application will be heavily
affected by use of the database (the major bottleneck). The application server must be
tuned to be optimized for the tests. Anyone carrying out such tests must therefore
have an in-depth knowledge of <emphasis>all</emphasis> the platforms they are
benchmarking if they have any chance of achieving meaningful results. The best test
you can make is to run your own application on JBoss under realistic load on realistic
hardware and decide whether it satisfies your performance needs. Remember also that
the highly customizable nature of the JBoss architecture means you have a lot more
flexibility when it comes modifying the server for performance tuning.</para> <!--
Todo: link to faq.cmp.diy as example -->
+ <para>Remember also that the saving you make in license fees by
using JBoss (potentially thousands of dollars per-cpu) can be invested in your
hardware budget instead. Keep this in mind if you are worried about performance.</para>
+
+ <para>IN the past, JBoss has been reported as being less scalable
purely because of its lack of clustering support. <link
id="faq.jboss.cluster">Clustering</link> is a key feature of JBoss 3.</para>
+
<para>TODO: Latest status of ECPerf??</para>
- <para>JBoss has been reported as being less scalable purely because
of its lack of clustering support. <link id="faq.jboss.cluster">Clustering</link> is a
key feature of JBoss 3</para>
+
</answer>
</qandaentry>
<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. TODO: Link to HA docs
(when they are available i.e. now).</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.org";>JavaGroups</ulink> framework. See the <link
linkend="clustering">clustering chapter</link> for more information.</para>
</answer>
</qandaentry>
@@ -264,6 +268,7 @@
<question><para>How do I install and run JBoss?</para></question>
<answer>
<para>Unpack the archive and run the appropriate script in
JBOSS_HOME/bin. TODO: Link to manual installation chapter.</para>
+ <para>If you have specific configuration issues see <xref
linkend="faq.admin"/></para>
</answer>
</qandaentry>
@@ -292,7 +297,7 @@
<qandaentry id="faq.jboss.soap">
<question><para>Does JBoss Support SOAP?</para></question>
<answer>
- <para>The previous soap implementation in JBoss, ZOAP, has been
dropped. Work is now underway (under the name JBoss.Net) to integrate the apache AXIS
(TODO: link) project into JBoss.</para>
+ <para>The previous soap implementation in JBoss, ZOAP, has been
dropped. Work is now underway (under the name JBoss.Net) to integrate the apache
<ulink url="http://xml.apache.org/axis/";>Axis</ulink> project into JBoss. (TODO: is
this correct? More on Web Services)</para>
</answer>
</qandaentry>
@@ -319,34 +324,47 @@
</qandadiv>
-<!-- Admin -->
+ <!-- Admin -->
<qandadiv id="faq.admin">
<title>Server Admin and Configuration</title>
- <para>Starting, stopping. Where to find the basic server configuration
files, what they contain etc. Monitoring services</para>
+ <para>Installation, starting, stopping. Where to find the basic server
configuration files, what they contain. Monitoring and instrumentation services
etc.</para>
<qandaentry id="faq.admin.shutdown">
<question><para>How do I cleanly shutdown JBoss?</para></question>
<answer>
<para><quote><command>^C</command></quote> and <quote><command>kill
<![CDATA[<pid>]]></command></quote> should both cause a clean shutdown.
-.</para>
+ .</para>
</answer>
</qandaentry>
+ <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 :
+ <![CDATA[
+ <mbean code="org.jboss.util.FileURLPatch"
name="DefaultDomain:service=FileURLPatch">
+ <attribute name="Enabled">true</attribute>
+ </mbean>
+ ]]>
+ </para>
+ </answer>
+ </qandaentry>
+
<qandaentry id="faq.admin.ntservice">
<question><para>How do I run JBoss as a service on Windows
NT</para></question>
<answer>
<para>In this respect, JBoss is no different to any other Java
application. There are various third-party solutions available to install Java
programs as NT services.</para>
-<!-- TODO: list some. Is the contrib module still in working order? Manual - link
to installation.
- * Running a Java 2 Application as an NT Service
- * JNT for Windows NT/2000
--->
+ <!-- TODO: list some. Is the contrib module still in working order?
Manual - link to installation.
+ * Running a Java 2 Application as an NT Service
+ * JNT for Windows NT/2000
+ -->
</answer>
</qandaentry>
<qandaentry>
<question><para>What files are used for server
configuration?</para></question>
<answer>
- <para>This is the answer.</para>
+ <para>answer.</para>
</answer>
</qandaentry>
@@ -360,7 +378,7 @@
<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.</para>
+ <para>Yes. Sun licensing issues forbid its commenrcial use.</para>
</answer>
</qandaentry>
@@ -372,7 +390,7 @@
<qandaentry id="faq.ejb.newbie">
<question><para>I'm new to EJB. Where can I find out
more?</para></question>
<answer>
- <para> See <link linkend="faq.general.ejb">above.</link> TODO: Link
to EJB tutorials and sources of info to be tried before jboss forums.</para>
+ <para> See <xref linkend="faq.general.ejb"/> above. TODO: Link to
EJB tutorials and sources of info to be tried before jboss forums.</para>
</answer>
</qandaentry>
@@ -453,7 +471,7 @@
<qandaentry>
<question><para>Does JBoss support the CMP features from EJB
2.0?</para></question>
<answer>
- <para>JBoss 3, yes? TODO.</para>
+ <para>Support for EJB 2.0 CMP is a central feature for JBoss
3.0</para>
</answer>
</qandaentry>
@@ -488,7 +506,7 @@
</qandadiv>
-<!-- Web container stuff -->
+ <!-- Web container stuff -->
<qandadiv id="faq.web">
<title>Web Applications</title>
@@ -524,10 +542,10 @@
</qandadiv>
-<!-- End of Web container stuff -->
+ <!-- End of Web container stuff -->
-<!-- Database stuff -->
+ <!-- Database stuff -->
<qandadiv>
<title>Databases</title>
<para>Is a separate section on DBs needed? Probably. How to use Oracle XA
impl etc.</para>
@@ -547,9 +565,9 @@
</qandadiv>
-<!-- End of Database stuff -->
+ <!-- End of Database stuff -->
-<!-- Security -->
+ <!-- Security -->
<qandadiv>
<title>Security</title>
<para>Security in JBoss, JBossSX, JAAS, Web integration, security proxies
etc.</para>
@@ -582,7 +600,7 @@
</qandaentry>
</qandadiv>
-<!-- end of Security -->
+ <!-- end of Security -->
<qandadiv>
<title>JBoss Architecture and Development.</title>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
