User: luke_t
Date: 01/11/15 14:03:59
Added: src/xdocs faq.xml
Log:
First import of the docbook version of the FAQ.
This is based on the original FAQ on the web page but is intended to provide more
information and be linked to the manual. It should hopefully be easier to maintain as
a docbook file in cvs. Errors in the FAQ could potentially be submitted through the
standard sourcefoge interfaces. It also has numbered sections, so the FAqs should be
easier to refer to by section number (though these aren't fixed yet).
It is still in a very early stage and not fit for public consumption - incorrect
information is probably more harmful than no information at all :). Feel free to
update any of the sections you feel you have expertise in.
Revision Changes Path
1.1 manual/src/xdocs/faq.xml
Index: faq.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<!-- !DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"docbookx/docbookx.dtd" -->
<article class="faq">
<articleinfo>
<title>JBoss FAQ</title>
<releaseinfo>$Revision: 1.1 $, $Date: 2001/11/15 22:03:59 $</releaseinfo>
<!--revhistory>
<revision>
<revnumber>$Revision: 1.1 $</revnumber>
<date>$Date: 2001/11/15 22:03:59 $</date>
</revision>
</revhistory>
-->
</articleinfo>
<!-- <abstract>
<para>
The abstract text...
</para>
</abstract>
-->
<qandaset defaultlabel="number">
<qandadiv id="faq.intro">
<title>Introduction</title>
<para>About the FAQ (where, what, who how etc.)</para>
<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>
</answer>
</qandaentry>
<qandaentry>
<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.
-->
</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 -->
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq.general">
<title>General</title>
<para>Basic questions about J2EE.</para>
<qandaentry id="faq.general.j2ee">
<question><para>What is Java 2 Enterprise Edition
(J2EE)?</para></question>
<answer>
<para>
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>JDBC data access API</para></listitem>
<listitem><para>Java Servlets</para></listitem>
<listitem><para>JavaServer Pages (JSP)</para></listitem>
<listitem><para>Java Transaction API (JTA)</para></listitem>
<listitem><para>Java Transaction Service
(JTS)</para></listitem>
<listitem><para>Java Messaging Service
(JMS)</para></listitem>
<listitem><para>Remote Method Invocation
(RMI)</para></listitem>
<listitem><para>CORBA</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>
</para>
</answer>
</qandaentry>
<qandaentry id="faq.general.ejb">
<question><para>What are Enterprise JavaBeans (EJB)?</para></question>
<answer>
<para>Enterprise JavaBeans (EJB) is a <ulink
url="http://java.sun.com/products/ejb/docs.html";>specification and
architecture</ulink> for the development and deployment of component-based,
distributed business applications on the Java platform. It is a significant part of
Java 2 Enterprise Edition (J2EE) - a unified architecture and platform for delivering
the benefits of the Java platform to the server-based computing environment.</para>
<para>A business component that is developed for the Enterprise
JavaBean architecture is also confusingly called an Enterprise JavaBean. These
components may be written once, and then deployed on any server platform that supports
the Enterprise JavaBeans specification. A key goal of the EJB architecture is to make
the job of developing EJB components and the client applications that access them very
simple indeed. Much of this is achieved by defining an architectural entity called a
<emphasis>container</emphasis> - an EJB container - that acts as a buffer between EJB
components and their client as well as between EJB components and the very complex
reality of developing scalable, distributed systems. An EJB container is itself
contained within an <emphasis>EJB server</emphasis>.
</para>
<para>Further information about Enterprise JavaBeans is available on
the <ulink url="http://java.sun.com/products/ejb/index.html";>Enterprise JavaBeans home
page</ulink></para>
</answer>
</qandaentry>
<qandaentry id="faq.general.javabeans">
<question><para>Are JavaBeans different from Enterprise
JavaBeans?</para></question>
<answer>
<para>
Yes, JavaBeans are very different from Enterprise JavaBeans
(EJBs). Both JavaBeans and EJBs are units of packaged functionality but they are
designed to function in very specific and different environments. JavaBeans facilitate
black box reuse of visual and non-visual components within JavaBean-aware IDEs. EJBs
on the other hand are non-visual components that can only be deployed in an
EJB-compliant Java application server.</para>
<para>JavaBeans are basically just classes executed in the JVM,
while EJBs are managed objects that are deployed within an EJB application server.
JavaBeans may be driven by events, but EJBs are currently just driven by remote method
calls.</para>
</answer>
</qandaentry>
<qandaentry id="faq.general.javaappserver">
<question><para>What is a Java Application Server?</para></question>
<answer>
<para>In the current context, a Java application server is a
sophisticated software system that provide a run-time environment for executing
components written in Java. The widespread adoption of the EJB standard from the J2EE
specification has ensured that a well written component can be without additional
development work deployed in almost all Java application servers.</para>
</answer>
</qandaentry>
<qandaentry id="faq.general.deployment">
<question><para>What does Deployment mean?</para></question>
<answer>
<para>Deployment is the act of preparing and sending the bean(s) to
the application server to become available as application components. In preparation
for deployment, any resources that the bean provider has used in the code must be
associated with real resources, transactional attributes may be specified, security
attributes may be set, and any other container-specific settings will all be specified
in deployment descriptors. The compiled code and the deployment descriptors will all
be jarred together into an application jar and then the jar will be placed in the
necessary location for the application server to use. The final act of deployment is
the application server parsing the deployment descriptors, preparing the container
environment, and then binding the bean names to the naming service to make them
available for calls.</para>
</answer>
</qandaentry>
<qandaentry id="faq.general.transmgmt">
<question><para>What is Transaction Management?</para></question>
<answer>
<para>
A transaction is an atomic and reliable unit of program
execution. Transactions systems are invaluable in any system that support concurrent
processing. For example, if multiple clients are using the same database table
concurrently, it's possible that the database write operations they perform could
leave the table in an inconsistent state. With transactional support, each user see a
transaction as an operation that either completes successfully or not at all. The
possibility of inconsistencies arising as result of their interleaved database
operations is removed.
</para>
<para>
The Enterprise JavaBeans architecture provides automatic
support for distributed transactions in component based applications. Such distributed
transactions can atomically update data in multiple databases. The burden of managing
transactions is thus shifted from the bean developer to the EJB container and/or
server.
</para>
<!-- TODO: Give ref and update to 2.0 -->
<para>Read chapter 11 of the EJB 1.1 spec if you are interested in
knowing more about Transaction Management.</para>
</answer>
</qandaentry>
<qandaentry id="faq.general.persistence">
<question><para>What is Bean/Container Managed
Persistence?</para></question>
<answer>
<para>With respect to Enterprise JavaBeans (EJBs), persistence is a
term that describes the process whereby the the state of an active (stateful?) EJB is
stored (usually to a database) in such a way that the EJB can be reactivated later. It
is serialization for EJBs if you like.</para>
<para>There are two flavours of persistence in EJB - Bean-Managed
Persistence (BMP) and Container-Managed Persistence (CMP). The main difference between
the two flavours is who is responsible for <emphasis>actually</emphasis> persisting
the EJB. In BMP the bean developer is responsible for writing the code that persists
the beans state (maybe using JDBC?) while in CMP, the container is reponsible. In CMP
a bean developer might not even <emphasis>know</emphasis> what object-relational
database persistence is let alone how it works?. Pretty neat.</para>
<para>A relevant excerpt from the <ulink
url="http://java.sun.com/products/ejb/docs.html";>EJB 1.1. specification</ulink>
itself, on page 100:
<blockquote><para>The entity bean component protocol allows
the entity Bean Provider either to implement the entity bean's persistence directly in
the entity bean class or in one or more helper classes provided with the entity bean
class (bean-managed persistence), or to delegate the entity bean's persistence to the
Container Provider tools used at deployment time (container-managed
persistence).</para></blockquote>
</para>
</answer>
</qandaentry>
<qandaentry id="faq.general.jmx">
<question><para>What are these MBeans and JMX that I keep hearing
about?</para></question>
<answer>
<para>...</para>
</answer>
</qandaentry>
</qandadiv>
<qandadiv>
<title>JBoss</title>
<para>General questions on JBoss, licensing, business/commercial benfits,
support, training and supported features.</para>
<qandaentry id="faq.jboss.summary">
<question><para>What is JBoss?</para></question>
<answer>
<para>Basically, JBoss is an application server written in Java that
can host business components developed in Java. The aim is to provide a high-quality,
freely available, open source implementation of the Java 2 Enterprise Edition (<link
linkend="faq.general.j2ee">J2EE</link>) specification. </para>
<para>The JBoss server is developed in the Open Source tradition by
volunteers and sponsors using 100% Pure Java</para>
<para>We are working very hard to ensure that JBoss rightfully
becomes <emphasis>the</emphasis> premier EJB server for the Java 2 Enterprise
Edition.</para>
</answer>
</qandaentry>
<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>
</answer>
</qandaentry>
<!-- TODO this faq should be modified to take the jboss group answer into
account, or perhaps removed altogether -->
<qandaentry id="faq.jboss.survival">
<question><para>How does JBoss Survive?</para></question>
<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>
</answer>
</qandaentry>
<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>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>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>
<answer>
<para>TODO: Link to jboss.org ref sites list.</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>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>
</answer>
</qandaentry>
<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>
</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>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.performance">
<question><para>Survey 'x' showed that JBoss didn't perform as well as
app-server 'y'. How scalable is JBoss and how well does it perform?</para></question>
<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>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>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.install">
<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>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.sell">
<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>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.distribute">
<question><para>Can I include JBoss in my
distribution?</para></question>
<answer>
<para>Yes JBoss is licensed under the LGPL which means that you are
entitled to redistribute our binary (jar files) free of charge without modifications.
You can distribute your code under any license you wish. If you need modifications of
the core JBoss code, talk to us.</para>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.iiop">
<question><para>Does JBoss support RMI/IIOP.</para></question>
<answer>
<para>RMI/IIOP is not supported in the JBoss 2.x series. Work is
underway to provide an implementation to be included in JBoss 3, using the free Java
orb <ulink url="http://www.jacorb.org";>JacORB</ulink>.</para>
</answer>
</qandaentry>
<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>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.jdks">
<question><para>Which JDK versions does JBoss
support?</para></question>
<answer>
<para>JDK 1.2+ is supported in JBoss 2.4.*. As of JBoss Version 3.0
you will need JDK 1.3 or later.</para>
</answer>
</qandaentry>
<qandaentry id="faq.jboss.remote">
<question><para>How do I get my client working from a remote
machine?</para></question>
<answer>
<para>TODO: Two things:Correct JNDI properties and client
libraries... jnp setting, jboss jar files.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Test Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
</qandadiv>
<!-- 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>
<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>
</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
-->
</answer>
</qandaentry>
<qandaentry>
<question><para>What files are used for server
configuration?</para></question>
<answer>
<para>This is the 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.</para>
</answer>
</qandaentry>
</qandadiv>
<qandadiv id="faq.ejb">
<title>EJB Development</title>
<para>General questions on EJB development with JBoss.</para>
<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>
</answer>
</qandaentry>
<qandaentry id="faq.ejb.deploy">
<question><para>What tasks must be completed to deploy an EJB using
JBoss?</para></question>
<answer>
<para>
<itemizedlist>
<listitem>
<para>Compile the bean classes and interfaces.</para>
</listitem>
<listitem>
<para>Create an <filename>ejb-jar.xml</filename> file
by hand or using a third-party tool. </para>
</listitem>
<listitem>
<para>If using Entity Beans with CMP, then use create
a jaws.xml file. TODO: make sure jaws.xml is described elsewhere. </para>
</listitem>
<listitem>
<para>If using resources, custom containers, or any
other JBoss specific configurations, then create a jboss.xml file.</para>
</listitem>
<listitem>
<para>Finally, jar the .xml files (note that they must
be in META-INF parent directory) and the .class files for the bean into a jar and copy
this to the JBoss deployment directory (JBOSS_HOME/deploy). Your application should be
deployed automatically.</para>
</listitem>
<listitem>
<para>Classes that the bean imports may be included in
the deployed jar, or they can be the JBOSS_HOME/lib/ext directory (in a jar
file).</para>
</listitem>
</itemizedlist>
TODO: link to manual here. Possibly remove the above list.
</para>
</answer>
</qandaentry>
<qandaentry id="faq.ejb.run">
<question><para>How can I run my EJB jar in JBoss?</para></question>
<answer>
<para>Once you have deployed your bean(s), they are ready to be
called by clients or other beans.</para>
</answer>
</qandaentry>
<qandaentry id="faq.ejb.jndienv">
<question><para>When do I need to prefix a JNDI lookup with
"java:comp/env"?</para></question>
<answer>
<para><quote>java:comp/env</quote> is the bean's <quote>Environment
Naming Context</quote> which is available for the bean's private use. It is not
globally available through JNDI. Information which is configured for the bean in the
<filename>ejb-jar.xml</filename> will be stored in this context, namely references to
other beans, resource references (e.g. datasources) and environment entries. When
looking these up from within the bean code, you should prefix the JNDI name that the
resource is bound to with <quote>java:comp/env</quote>.
</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>What's an EAR file and when should I use
one?</para></question>
<answer>
<para>An <quote>ear</quote> file is a jar archive which contains a
complete J2EE application consisting of both ejbs (as a .jar file) and a <link
linkend="faq.web">web application</link> (as a .war file).</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
</qandadiv>
<!-- End of EJB section -->
<qandadiv>
<title>Container-Managed Persistence (CMP)</title>
<para>CMP implementations, spec versions etc.</para>
<qandaentry>
<question><para>What is CMP and how do I use it with
JBoss?</para></question>
<answer>
<para>Default impl - link to manual.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Does JBoss support the CMP features from EJB
2.0?</para></question>
<answer>
<para>JBoss 3, yes? TODO.</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>
</answer>
</qandaentry>
<qandaentry id="faq.cmp.diy">
<question><para>Write my own persistence layer? Why would I want to do
that? How would I go about it?</para></question>
<answer>
<para>Optimize for your own entity data. Point to File-based impl -
TODO: is this in the manual?</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>...</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>...</para>
</answer>
</qandaentry>
</qandadiv>
<!-- 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>
<qandaentry id="faq.web.jboss">
<question><para>What about the J2EE web-tier, how is that implemented
in JBoss?</para></question>
<answer>
<para>JBoss 2.x is primarily an EJB server. Support for the full
J2EE stack is provided through integration with third party web containers.
Pre-configured, bundled versions are available for download which provide integration
with Tomcat and Jetty</para>
<para>In JBoss 3.0, Jetty will be more tightly integrated and will
be included as the default web container.</para>
</answer>
</qandaentry>
<qandaentry id="faq.web.apache">
<question><para>How do I integrate JBoss/Tomcat with the Apache Web
Server?</para></question>
<answer>
<para>...</para>
</answer>
</qandaentry>
<qandaentry id="faq.web.security">
<question><para>How does security work with the integrated web
containers?</para></question>
<answer>
<para>Integration with JBoss security. Link to security section and
manual. Stress downloading of pre-configured bundles.</para>
</answer>
</qandaentry>
<qandaentry id="faq.web.jbosswebfile">
<question><para>What is <filename>jboss-web.xml</filename>
for?</para></question>
<answer>
<para>...</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>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</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>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
</qandadiv>
<!-- end of Security -->
<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>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question><para>Question.</para></question>
<answer>
<para>This is the answer.</para>
</answer>
</qandaentry>
</qandadiv>
</qandaset>
</article>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
