You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by hu...@apache.org on 2006/02/11 04:19:44 UTC
svn commit: r376916 - in /struts/site/trunk/xdocs: helping.fml helping.xml
kickstart.fml kickstart.xml
Author: husted
Date: Fri Feb 10 19:19:42 2006
New Revision: 376916
URL: http://svn.apache.org/viewcvs?rev=376916&view=rev
Log:
FAQ Plugin
* Migrate Kickstart and How to Help FAQ to plugin format.
Added:
struts/site/trunk/xdocs/helping.fml
- copied, changed from r376838, struts/site/trunk/xdocs/helping.xml
struts/site/trunk/xdocs/kickstart.fml
- copied, changed from r376838, struts/site/trunk/xdocs/kickstart.xml
Removed:
struts/site/trunk/xdocs/helping.xml
struts/site/trunk/xdocs/kickstart.xml
Copied: struts/site/trunk/xdocs/helping.fml (from r376838, struts/site/trunk/xdocs/helping.xml)
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/helping.fml?p2=struts/site/trunk/xdocs/helping.fml&p1=struts/site/trunk/xdocs/helping.xml&r1=376838&r2=376916&rev=376916&view=diff
==============================================================================
--- struts/site/trunk/xdocs/helping.xml (original)
+++ struts/site/trunk/xdocs/helping.fml Fri Feb 10 19:19:42 2006
@@ -16,91 +16,27 @@
<!--
// ======================================================================== 78
-->
-<document>
+<faqs title="How to Help FAQ">
- <properties>
- <title>How to Help FAQ</title>
- </properties>
-
- <body>
-
- <a name="faq"/>
- <section name="How to Help FAQ">
-
- <p align="center">
- "You can't always get what you want /
- <br/>
- but if you try real hard /
- <br/>
- you might just find /
- <br/>
- that you get what you need".
- <br/>
- [Rolling Stones]
- </p>
-
- <a name="contents"/>
- <subsection name="Topics">
-
- <ul>
- <li>
- <a href="#involved">
- How can I get involved with Apache Struts?
- </a>
- </li>
- <li>
- <a href="#bugs">
- How do I join the mailing lists?
- </a>
- </li>
- <li>
- <a href="#corp">
- What can my company do to help support Apache
- Struts?
- </a>
- </li>
- <li>
- <a href="#patches">
- How can I create a patch?
- </a>
- </li>
- <li>
- <a href="#bugs">
- How can I report bugs or make feature suggestions?
- </a>
- </li>
- <li>
- <a href="#contribute">
- How can I contribute to the Apache Struts source
- code?
- </a>
- </li>
- <li>
- <a href="#documentation">
- How can I contribute to the documentation?
- </a>
- </li>
- <li>
- <a href="#release">
- So when is the next release coming out?
- </a>
- </li>
- <li>
- <a href="#release_help">
- How can I help the next release along?
- </a>
- </li>
- <li>
- <a href="#decisions">
- How can I help make the decisions?
- </a>
- </li>
- </ul>
-
- </subsection>
-
- <a name="involved"/>
- <subsection name="Getting Involved">
+ <part>
+ <p align="center">
+ "You can't always get what you want /
+ <br/>
+ but if you try real hard /
+ <br/>
+ you might just find /
+ <br/>
+ that you get what you need".
+ <br/>
+ [Rolling Stones]
+ </p>
+ </part>
+
+ <part>
+
+ <faq id="involved">
+ <question>Getting Involved</question>
+ <answer>
<p>
Every volunteer project obtains its strength
@@ -171,10 +107,12 @@
Your feedback helps the technology to evolve.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="mail"/>
- <subsection name="Joining the Mailing Lists">
+ <faq id="mail">
+ <question>Joining the Mailing Lists</question>
+ <answer>
<p>
There are a variety of ways to participate.
@@ -212,12 +150,13 @@
HTML</a>
in your email client before posting.
</p>
- </subsection>
-
+ </answer>
+ </faq>
- <a name="corp"/>
- <subsection
- name="What can my company do to help support Apache Struts?">
+ <faq id="corp">
+ <question>What can my company do to help support Apache
+ Struts?</question>
+ <answer>
<p>
Apache Struts is an all volunteer product.
Our customers are the volunteers who donate their time and
@@ -289,10 +228,12 @@
represents.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="patches"/>
- <subsection name="How do I create a patch?">
+ <faq id="patches">
+ <question>How do I create a patch?</question>
+ <answer>
<p>
A patch is a machine-readable script that can
automatically
@@ -358,10 +299,12 @@
subject of creating patches.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="bugs"/>
- <subsection name="How can I report bugs or suggest features?">
+ <faq id="bugs">
+ <question>How can I report bugs or suggest features?</question>
+ <answer>
<p>
Tracking of bug reports and enhancement suggestions for
Apache Struts
@@ -480,11 +423,13 @@
</li>
</ul>
- </subsection>
+ </answer>
+ </faq>
- <a name="contribute"/>
- <subsection
- name="How can I contribute to the Struts source code?">
+ <faq id="contribute">
+ <question>How can I contribute to the Struts source
+ code?</question>
+ <answer>
<p>
A very good place to start is by
@@ -553,13 +498,17 @@
if we achieve this).
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="documentation"/>
- <subsection name="How can I contribute to the documentation?">
+ <faq id="documentation">
+ <question>How can I contribute to the
+ documentation?</question>
+ <answer>
<p>
- The documentation is maintained in the repository under
+ The documentation is maintained in the repository
+ under
the
<code>xdocs</code>
folder for the subproject.
@@ -567,7 +516,8 @@
change to the subprojects trunk directory and run
<code>maven site</code>
.
- The Maven build compiles the site and stores the output
+ The Maven build compiles the site and stores the
+ output
under
<code>target/docs/</code>
.
@@ -576,16 +526,19 @@
<p>
Procedurally, the only difference between patching
documentation and
- software is that the docs are kept in XML rather than Java
+ software is that the docs are kept in XML rather than
+ Java
source code.
Otherwise, all the same instructions pertain.
</p>
<p>
- If you would like to help with the documentation, it is
+ If you would like to help with the documentation, it
+ is
important to
provide patches and new pages in the XML source.
- Otherwise, some other volunteer will have to do this for
+ Otherwise, some other volunteer will have to do this
+ for
you, and it may
never get done.
(Sad but true.)
@@ -594,7 +547,8 @@
<p>
If you are submitting new material, it is important to
decide exactly
- where you would put this in relation to the rest of the
+ where you would put this in relation to the rest of
+ the
documentation.
Again, someone has to figure that out before it can be
added,
@@ -602,23 +556,29 @@
</p>
<p>
- If you are making a substantial contribution, such as a
+ If you are making a substantial contribution, such as
+ a
new HOW-TO,
- please consider submitting a document in the XML format we
+ please consider submitting a document in the XML
+ format we
use.
- This will make it easier to add your contribution to the
+ This will make it easier to add your contribution to
+ the
official
documentation so that it becomes part of a Struts
distribution.
</p>
<p>
- The trick to getting started is to download the nightly
+ The trick to getting started is to download the
+ nightly
build and try
building the subproject's site.
- Then try adding your own XML page under xdocs/ to see if
+ Then try adding your own XML page under xdocs/ to see
+ if
the build succeeds.
- If it doesn't, it will report where the bad element is,
+ If it doesn't, it will report where the bad element
+ is,
much like it reports
where a bad programming expression is.
If it does, then your page should be available under
@@ -629,15 +589,18 @@
To display markup, substitute &lt; for <.
The unmatched trailing > will be ignored.
Since it is XML, all elements also need to closed.
- So elements like <br> and <hr> need to set out as
+ So elements like <br> and <hr> need to set out
+ as
<br/> and <hr/>.
</p>
<p>
- Also watch for the length of code samples - these do not
+ Also watch for the length of code samples - these do
+ not
wrap.
If a line is too long,
- it will force the right margin out past the edge of the
+ it will force the right margin out past the edge of
+ the
screen or
printed page.
</p>
@@ -648,10 +611,12 @@
<a href="wiki.apache.org/struts/">Struts Wiki</a>
.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="release"/>
- <subsection name="So when is the next release coming out?">
+ <faq id="release">
+ <question>So when is the next release coming out?</question>
+ <answer>
<p>
Here is the truth regarding releases:
@@ -660,11 +625,14 @@
<p>
Apache products are released on the basis of merit,
and ~not~ according to a strict timetable.
- The volunteers devote whatever time they can to work on
+ The volunteers devote whatever time they can to work
+ on
the product.
- But all volunteers have real jobs and real lives, that do
+ But all volunteers have real jobs and real lives, that
+ do
take precedence.
- Since Struts does not have paid personnel working on the
+ Since Struts does not have paid personnel working on
+ the
project,
we simply cannot make date-oriented commitments.
</p>
@@ -680,7 +648,8 @@
<p>
That may sound flip, but it ~is~ the truth.
- The delivery of production-quality, leading-edge software
+ The delivery of production-quality, leading-edge
+ software
is
not something anyone can prognosticate.
If anyone tries, they are lying to you.
@@ -693,9 +662,11 @@
it is developed.
This way you can judge for yourself how quickly the
development is
- proceeding, and whether what is being developed will meet
+ proceeding, and whether what is being developed will
+ meet
your needs.
- If you need a feature right now, you can use the nightly
+ If you need a feature right now, you can use the
+ nightly
build, or roll
your own patch.
There are no internal code repositories, private
@@ -717,32 +688,40 @@
and you will have access to all the latest patches or
enhancements.
(Just like we were working down the hall.)
- If you can only ship your application based on a release
+ If you can only ship your application based on a
+ release
build of Struts,
- then you should base your development on the release build
+ then you should base your development on the release
+ build
of Struts,
and keep an eye on what is coming down the pipeline.
This way you are at least forewarned and forearmed.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="release_help"/>
- <subsection name="What can I do to help the next release along?">
+ <faq id="release_help">
+ <question>What can I do to help the next release
+ along?</question>
+ <answer>
<ul>
<li>
- Most importantly, download the latest nightly build or
+ Most importantly, download the latest nightly
+ build or
development release
and test it against your own applications.
Report any and all issues or suspected issues to
<a href="http://issues.apache.org/bugzilla">
Bugzilla</a>
.
- The sooner we resolve any problems, the fewer betas or
+ The sooner we resolve any problems, the fewer
+ betas or
release candidates
we will have to distribute before we are done.
- (How do we know when we're done? -- When we run out of
+ (How do we know when we're done? -- When we run
+ out of
issues =:o)
The sooner we find them, the sooner we are done.)
</li>
@@ -754,12 +733,15 @@
.
The closer we get to a release, the more we worry
about breaking something.
- The more tests we have, the more confident we can be
+ The more tests we have, the more confident we can
+ be
when applying patches.
- Tests that prove that a pending issue is actually a
+ Tests that prove that a pending issue is actually
+ a
bug are the most
welcome ones.
- But we are eager for any and all tests for any and all
+ But we are eager for any and all tests for any and
+ all
features,
even those that still work =:0).
</li>
@@ -769,26 +751,34 @@
at
<a href="#bugs">Bugzilla</a>
.
- If there are any to which you can respond, please do.
- If there any patches posted, feel free to test them
+ If there are any to which you can respond, please
+ do.
+ If there any patches posted, feel free to test
+ them
your system,
- report the results, and cast your vote if they work.
+ report the results, and cast your vote if they
+ work.
</li>
<li>
<strong>Confirm an issue's category and
status</strong>
.
- Newbies often post feature suggestions or help-desk
+ Newbies often post feature suggestions or
+ help-desk
questions as "bugs".
- This bloats the list of fixes we (apparently) need to
+ This bloats the list of fixes we (apparently) need
+ to
apply before the next
- beta, making it hard to see the forest for the trees.
- If an issue doesn't seem to be categorized correctly,
+ beta, making it hard to see the forest for the
+ trees.
+ If an issue doesn't seem to be categorized
+ correctly,
exercise your best judgment and change it.
If one ticket seems like a duplicate of another,
go ahead and enter the change.
- Every modification to the ticket is echoed to the DEV
+ Every modification to the ticket is echoed to the
+ DEV
list and
automatically subjected to peer review.
Err on the side of doing.
@@ -798,7 +788,8 @@
Use Bugzilla to
<strong>vote for issues</strong>
you feel should be handle first.
- If an issue on your ballot doesn't include a patch,
+ If an issue on your ballot doesn't include a
+ patch,
feel free to try coding one yourself.
(In a meritocracy, patches are the only votes that
matter.)
@@ -808,19 +799,24 @@
</li>
<li>
- <strong>Answer questions on the user list.</strong>
- The Committers only have a limited amount of time to
+ <strong>Answer questions on the user
+ list.</strong>
+ The Committers only have a limited amount of time
+ to
volunteer.
- If Developers are supporting each other on the lists,
+ If Developers are supporting each other on the
+ lists,
the Committers have more time to spend on the next
release.
</li>
</ul>
- </subsection>
+ </answer>
+ </faq>
- <a name="decides_help"/>
- <subsection name="How can I help make the decisions?">
+ <faq id="decides_help">
+ <question>How can I help make the decisions?</question>
+ <answer>
<p>
A guiding principle of the Apache Software Foundation is
@@ -892,16 +888,18 @@
.
</p>
- </subsection>
+ </answer>
+ </faq>
+
+ </part>
+
+ <part>
- </section>
+ <p class="right">
+ <strong>Next:</strong>
+ <a href="mail.html">Mailing Lists</a>
+ </p>
- <section>
- <p class="right">
- <strong>Next:</strong>
- <a href="mail.html">Mailing Lists</a>
- </p>
- </section>
+ </part>
- </body>
-</document>
+</faqs>
Copied: struts/site/trunk/xdocs/kickstart.fml (from r376838, struts/site/trunk/xdocs/kickstart.xml)
URL: http://svn.apache.org/viewcvs/struts/site/trunk/xdocs/kickstart.fml?p2=struts/site/trunk/xdocs/kickstart.fml&p1=struts/site/trunk/xdocs/kickstart.xml&r1=376838&r2=376916&rev=376916&view=diff
==============================================================================
--- struts/site/trunk/xdocs/kickstart.xml (original)
+++ struts/site/trunk/xdocs/kickstart.fml Fri Feb 10 19:19:42 2006
@@ -16,121 +16,13 @@
<!--
// ======================================================================== 78
-->
-<document>
- <properties>
- <title>Kickstart FAQ</title>
- </properties>
- <body>
- <a name="faq"/>
- <section name="Kickstart FAQ">
-
- <a name="contents"/>
- <subsection name="Index">
-
- <p>
- Here are answers to the some of the usual Apache Struts
- getting-started questions.
- </p>
- <ul>
- <li>
- <a href="#shale">Why are you offering both Struts
- Shale and Struts Action Framework? Don't they
- compete for new development?</a>
- </li>
- <li>
- <a href="#2x">Is Shale likely to become Struts
- 2.x?</a>
- </li>
- <li>
- <a href="#fork">Is Struts Shale a fork?</a>
- </li>
- <li>
- <a href="#struts">If Shale is a new product, why is it
- called Struts?</a>
- </li>
- <li>
- <a href="#ti">What about Ti? What about WebWork?</a>
- </li>
- <li>
- <a href="#ti2">Does Ti mean there will be three
- frameworks?</a>
- </li>
- <li>
- <a href="#overdrive">What about OverDrive or Struts
- Nexus?</a>
- </li>
- <li>
- <a href="#classic">What's the difference between
- Struts Action Framework and Struts Classic</a>
- </li>
- </ul>
- <ul>
- <li>
- <a href="#struts">Why is the project called
- Struts?</a>
- </li>
- <li>
- <a href="#license">How is Apache Struts licensed?</a>
- </li>
- <li>
- <a href="#usage">Can Apache Struts be used in a
- commercial application?</a>
- </li>
- <li>
- <a href="#credits">Do I have to credit Apache Struts
- on my own website?</a>
- </li>
- </ul>
- <ul>
- <li>
- <a href="#requests">If a product doesn't do what I
- want, can I request that a feature be added?</a>
- </li>
- <li>
- <a href="#help">Where can I get help with Apache
- Struts?</a>
- </li>
- <li>
- <a href="#support">Is commercial support available for
- Apache Struts?</a>
- </li>
- <li>
- <a href="#providers">Are there ISPs that will host my
- Apache Struts application?</a>
- </li>
- <li>
- <a href="#ide">Is there a particularly good IDE to use
- with Struts Action Framework?</a>
- </li>
- </ul>
- <ul>
- <li>
- <a href="#digest">Is there a digest for the Apache
- Struts User list?</a>
- </li>
- <li>
- <a href="#newsgroup">Is there a Apache Struts
- Newsgroup?</a>
- </li>
- <li>
- <a href="#mailbounce">Why didn't my posting show up on
- the user list?"</a>
- </li>
- <li>
- <a href="#unsubscribe">How do I unsubscribe from the
- mailing list?</a>
- </li>
- </ul>
-
- <p>
- For other FAQs, see the documentation for each subproject.
- </p>
-
- </subsection>
-
- <a name="shale"/>
- <subsection
- name="Why are you offering both Struts Shale and Struts Action Framework? Don't they compete for new development?">
+<faqs title="Kickstart FAQ">
+ <part>
+
+ <faq id="shale">
+ <question>Why are you offering both Struts Shale and Struts Action
+ Framework? Don't they compete for new development?</question>
+ <answer>
<p>We do offer Apache Struts developers a choice, but, hey,
choice is good. :)</p>
<p>People who want to create and maintain the
@@ -157,10 +49,12 @@
to help page</a>
.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="fork"/>
- <subsection name="Is Struts Shale a fork?">
+ <faq id="fork">
+ <question>Is Struts Shale a fork?</question>
+ <answer>
<p>No. It's an entirely new product with its own architecture.
Struts Shale is an MVC framework for web applications,
like Struts Action Framework, but it's a fresh start.
@@ -171,11 +65,13 @@
volunteers ready to contribute.</p>
<p>We encourage you to choose the framework that works best
for you. (Even if it is not one of ours!)</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="struts"/>
- <subsection
- name="If Shale is a new product, why is it called Struts?">
+ <faq id="struts">
+ <question>If Shale is a new product, why is it called
+ Struts?</question>
+ <answer>
<p>
Apache Struts embraces standards, and JavaServer Faces
(JSF) is a new standard.
@@ -204,10 +100,12 @@
Since Shale does for JSF what Action does for JSP, we
consider Shale to be another Struts framework.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="2x"/>
- <subsection name="Is Shale likely to become Struts 2.x?">
+ <faq id="2x">
+ <question>Is Shale likely to become Struts 2.x?</question>
+ <answer>
<p>
Struts Shale has its own identity and its own release
cycle.
@@ -216,10 +114,12 @@
So, no, it is not likely that Struts Shale will become
Struts Action 2.x.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="ti"/>
- <subsection name="What about Ti? What about WebWork?">
+ <faq id="ti">
+ <question>What about Ti? What about WebWork?</question>
+ <answer>
<p>
<a href="http://wiki.apache.org/struts/StrutsTi">Struts
Ti</a>
@@ -265,10 +165,12 @@
Both a migration layer and migration documentation are
under active development.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="ti2"/>
- <subsection name="Does Ti mean there will be three frameworks?">
+ <faq id="ti2">
+ <question>Does Ti mean there will be three frameworks?</question>
+ <answer name="Does Ti mean there will be three frameworks?">
<p>
Probably not.
Like many projects, we start by giving proposed
@@ -278,10 +180,12 @@
If Struts Ti is accepted as Struts Action Framework 2.x,
the codename would fall into disuse.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="overdrive"/>
- <subsection name="What about OverDrive or Struts Nexus?">
+ <faq id="overdrive">
+ <question>What about OverDrive or Struts Nexus?</question>
+ <answer>
<p>
<a href="http://wiki.apache.org/struts/StrutsOverDrive">
OverDrive</a>
@@ -304,11 +208,13 @@
The codebase underlying the proposal is being coded in C#,
but a version for Java is expected in due course.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="action"/>
- <subsection
- name="What's the difference between Struts Action Framework and Struts Classic?">
+ <faq id="action">
+ <question>What's the difference between Struts Action Framework
+ and Struts Classic?</question>
+ <answer>
<p>For the Struts Action Framework 1.3.x series, we subdivided
the monolithic Struts 1.2.x distribution into several
discrete subprojects. Struts Classic is a codename for the
@@ -321,39 +227,47 @@
Framework Library". This bundle includes the original
"seven dwarfs" and new subprojects, like Struts
Scripting.</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="struts"/>
- <subsection name="Why is the project called Struts?">
+ <faq id="struts">
+ <question>Why is the project called Struts?</question>
+ <answer>
<p>It's a reference to struts in the architectural sense, a
reminder of the nearly invisible pieces that hold up
buildings, houses, and bridges.</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="license"/>
- <subsection name="How is Apache Struts licensed?">
+ <faq id="license">
+ <question>How is Apache Struts licensed?</question>
+ <answer>
<p>All Apache Struts products are copyrighted software
available under the
<a href="http://www.apache.org/licenses">Apache
License</a>
, a "free-to-use, business-friendly license".
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="usage"/>
- <subsection
- name="Can Apache Struts be used in a commercial product?">
+ <faq id="usage">
+ <question>Can Apache Struts be used in a commercial
+ product?</question>
+ <answer>
<p>Yes. The only requirements you must meet are those listed
in the
<a href="http://www.apache.org/licenses">Apache
License</a>
.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="credits"/>
- <subsection
- name="Do I have to credit Apache Struts on my own website?">
+ <faq id="credits">
+ <question>Do I have to credit Apache Struts on my own
+ website?</question>
+ <answer>
<p>You need to credit Apache Struts if you
<strong>redistribute your own framework</strong>
based on our products
@@ -369,11 +283,13 @@
Required if you've used the source code to create your own
server that you are redistributing to other people.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="requests"/>
- <subsection
- name="If a product doesn't do what I want, can I request that a feature be added?">
+ <faq id="requests">
+ <question>If a product doesn't do what I want, can I request that
+ a feature be added?</question>
+ <answer>
<p>
First, it's important to remember that Apache Struts is an
all-volunteer project.
@@ -401,10 +317,12 @@
the feature in your own application. (Which is what open
source is ~really~ all about.)
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="help"/>
- <subsection name="Where can I get help with Apache Struts?">
+ <faq id="help">
+ <question>Where can I get help with Apache Struts?</question>
+ <answer>
<p>Struts Action Framework comes complete with a
<a href="../userGuide/index.html">Users Guide</a>
to
@@ -438,31 +356,37 @@
in your
email client before posting.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="support"/>
- <subsection name="Is commercial support available?">
+ <faq id="support">
+ <question>Is commercial support available?</question>
+ <answer>
<p>The Apache Software Foundation does not provide commercial
support for any of our software products, including Apache
Struts products.
However, third parties may offer different degrees of
support.</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="providers"/>
- <subsection
- name="Are there ISPs that will host my Struts application?">
+ <faq id="providers">
+ <question>Are there ISPs that will host my Struts
+ application?</question>
+ <answer>
<p>For a listing of some Java and Struts Action Framework
ISPs, visit the
<a href="http://struts.sf.net/community/index.html">Struts
Community Resources</a>
area on SourceForge.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="ide"/>
- <subsection
- name="Is there a particularly good IDE to use with Struts Action Framework">
+ <faq id="ide">
+ <question>Is there a particularly good IDE to use with Struts
+ Action Framework"</question>
+ <answer>
<p>
Struts should work well with any development environment
that you would like to use, as well as with any
@@ -485,10 +409,12 @@
<a href="../faqs/index.html">Howto Guides</a>
for more about configuring IDEs to work with Struts.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="digest"/>
- <subsection name="Is there a digest for the User list?">
+ <faq id="digest">
+ <question>Is there a digest for the User list?</question>
+ <answer>
<p>
Yes.
<a href="mailto:user-digest-subscribe@struts.apache.org">
@@ -505,10 +431,12 @@
<a href="mailto:user@struts.apache.org">user list</a>
rather than trying to reply to the digest.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="newsgroup"/>
- <subsection name="Is there an Apache Struts newsgroup?">
+ <faq id="newsgroup">
+ <question>Is there an Apache Struts newsgroup?</question>
+ <answer>
<p>
Not a usenet group, but the Struts User list can be
accessed with your
@@ -520,11 +448,13 @@
<code>gmane.comp.jakarta.struts.user</code>
for the user list.
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="mailbounce"/>
- <subsection
- name="Why didn't my posting show up on the user list?">
+ <faq id="mailbounce">
+ <question>Why didn't my posting show up on the user
+ list?</question>
+ <answer>
<p>
You must be subscribed to the
<a href="mailto:user-subscribe@struts.apache.org">user
@@ -537,10 +467,12 @@
<a href="http://news.gmane.org">GMane Newsgroups</a>
instead).
</p>
- </subsection>
+ </answer>
+ </faq>
- <a name="unsubscribe"/>
- <subsection name="How do I unsubscribe from the mailing list?">
+ <faq id="unsubscribe">
+ <question>How do I unsubscribe from the mailing list?</question>
+ <answer>
<p>
<strong>From the email account used to subscribe to the
list,</strong>
@@ -560,16 +492,16 @@
>
instead.
</p>
- </subsection>
+ </answer>
+ </faq>
- </section>
+ </part>
- <section>
- <p class="right">
- <strong>Next:</strong>
- <a href="helping.html">How to Help FAQ</a>
- </p>
- </section>
+ <part>
+ <p class="right">
+ <strong>Next:</strong>
+ <a href="helping.html">How to Help FAQ</a>
+ </p>
+ </part>
- </body>
-</document>
+</faqs>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org