husted 2002/10/20 10:06:09
Modified: doc status.xml news.xml newbie.xml kickstart.xml
helping.xml
Log:
Add link from Roadmap to stuts-faces proposal. Update FAQs.
Revision Changes Path
1.4 +2 -1 jakarta-struts/doc/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- status.xml 17 Oct 2002 22:35:55 -0000 1.3
+++ status.xml 20 Oct 2002 17:06:08 -0000 1.4
@@ -100,6 +100,7 @@
<section href="proposals" name="Relevant Proposals">
<ul>
+<li><a href="../proposals/struts-faces.html">struts-faces taglib</a></li>
<li><a href="proposals/release-plan-1.1b2.html">Release Plan 1.1-b2</a></li>
<li><a href="proposals/workflow.html">Workflow Proposal</a></li>
</ul>
1.19 +2 -3 jakarta-struts/doc/news.xml
Index: news.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/news.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- news.xml 18 Oct 2002 15:27:41 -0000 1.18
+++ news.xml 20 Oct 2002 17:06:08 -0000 1.19
@@ -133,7 +133,7 @@
</p>
<p>
<a
href="http://easystruts.sourceforge.net";>http://easystruts.sourceforge.net</a><br/>
-<a
href="http://sourceforge.net/projects/easystruts";>http://easystruts.sourceforge.net</a>
+<a
href="http://sourceforge.net/projects/easystruts";>http://sourceforge.net/projects/easystruts</a>
</p>
<hr size="1" noshade=""/>
@@ -149,7 +149,7 @@
- [FIX] When element removed from Editor UI, elements wasn't removed in xml
source.<br/>
- [FIX] Synchronisation with Easy Struts wizards when editor is open.<br/>
- [FIX] When editor is re-open (after closed), struts-config.xml was in read only
mode.<br/>
- - [FIX] Some editor bugs... I include some screenshots
:http://easystruts.sourceforge.net/editor.htmlhttp://easystruts.sourceforge.net<br/>
+ - [FIX] Some editor bugs... I include some screenshots:<a
href="http://easystruts.sourceforge.net/editor.html";>http://easystruts.sourceforge.net</a><br/>
</p>
<hr size="1" noshade=""/>
@@ -163,7 +163,6 @@
<a
href="http://www.jamesholmes.com/struts/struts-console-2.1.zip";>http://www.jamesholmes.com/struts/struts-console-2.1.zip</a><br/>
-- OR --<br/>
<a
href="http://www.jamesholmes.com/struts/struts-console-2.1.tar.gz";>http://www.jamesholmes.com/struts/struts-console-2.1.tar.gz</a><br/>
-http://www.jamesholmes.com/struts/struts-console-2.1.tar.gz
</p>
<p>
Struts Console is FREE software.
1.11 +40 -0 jakarta-struts/doc/newbie.xml
Index: newbie.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/newbie.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- newbie.xml 12 Oct 2002 16:51:26 -0000 1.10
+++ newbie.xml 20 Oct 2002 17:06:08 -0000 1.11
@@ -23,6 +23,8 @@
<li>Do I have to have a separate ActionForm bean for every HTML form?</li>
+ <li>do ActionForms have to be true JavaBeans?</li>
+
<li>Can I use other beans or hashmaps with ActionForms?</li>
<li>How can I prepopulate a form?</li>
@@ -135,6 +137,16 @@
</section>
+<section href="JavaBeans" name="Do ActionForms have to be true JavaBeans?">
+<p>
+The utilities that Struts uses (Commons-BeanUtils since 1.1) require that
ActionForm properties follow
+the JavaBean patterns for mutators and accessors (get*,set*,is*). Since Struts uses
the Introspection API
+with the ActionForms, some containers may require that all the JavaBean patterns be
followed, including
+declaring "<code>implements serializable</code>" for each subclass. The safest
thing is to review the
+<a href="userGuide/preface.html#javabeans">JavaBean specification</a> and follow
all the prescribed patterns.</p>
+</section>
+
+
<section href="multiple" name="Can I use multiple HTML form elements with the same
name?">
<p>
Yes. Define the element as an array and Struts will autopopulate it like any other.
@@ -227,6 +239,34 @@
</section>
<section name="How do I access my database?">
+<p>
+The best thing is use the Action as a thin adaptor between the
web/presentation-tier and your business classes
+(including those that access a database).
+</p>
+<p>
+So you first design a business API that uses plain Java classes. The best thing is
to use objects that take
+ordinary Java types and return a JavaBean or collection of JavaBeans. The Action
then calls these objects and
+passes the result back to the web/presentation tier.
+</p>
+<p>
+A common approach is to create an Action class for each of the business API
methods/classes that you need to call.
+Ideally, all the database access code should be encapsulated in the business API
classes, so Struts doesn't know
+what persistent layer you are using (or even if there is a persisentance layer). It
just passes a key or search
+String and gets back a bean or collection of beans. This lets you use the same
business API classes in other
+environments, and also to run unit tests against your business API outside of
Struts or a HTTP environment.
+</p>
+<p>
+To get started, it's simplest to setup a 1:1 correspondence between the Actions and
the entry-points to
+your business API. As you gain experience, you will find ways to combine your
Actions, say by using the
+DispatchAction. It's even possible to use a single "framework" Action to call all
of your business
+classes, as is done with Scaffold ProcessAction in the contrib folder. Using fewer
Actions does require
+a deeper understanding of how Struts and MVC frameworks operate. Don't hestitate to
err on the side
+of creating more Actions at first. The Struts configuration makes it easy to
refactor your Actions
+later, since you can change the Action type without changing anything else in the
application.
+</p>
+<p>
+For more, see
+</p>
<p>
<a
href="http://www.mail-archive.com/struts-user@;jakarta.apache.org/msg24621.html">http://www.mail-archive.com/struts-user@;jakarta.apache.org/msg24621.html</a><br/>
<a
href="http://www.mail-archive.com/struts-user@;jakarta.apache.org/msg24709.html">http://www.mail-archive.com/struts-user@;jakarta.apache.org/msg24709.html</a><br/>
1.19 +36 -6 jakarta-struts/doc/kickstart.xml
Index: kickstart.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/kickstart.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- kickstart.xml 12 Oct 2002 16:51:26 -0000 1.18
+++ kickstart.xml 20 Oct 2002 17:06:08 -0000 1.19
@@ -188,27 +188,50 @@
<p>Development of both products began about the same time. Leading up to the
release of 1.0, it was thought better to continue to develop the taglibs alongside the
controller. Now that 1.0 is out, the Java ServerPages Standard Taglib is in active
development. Once work on the JSPTL stabilizes, the Struts taglibs will be revisited.
Tags which are not linked directly to the framework may be hosted at Jakarta Taglibs
instead.</p>
</section>
+<section href="xhtml" name="Are the Struts tags XHTML compliant?">
+<p>If you utilize a <html:html xhtml="true> element on your page, the tags
+will render in a XHTML compatible manner (since Struts 1.1 beta 2). </p>
+</section>
+
+<section href="wml" name="Will the Struts tags support other markup languages such
as WML">
+<p>
+Struts itself is markup neutral. The original Struts taglibs are only one example
of how
+presentation layer components can access the framework. The framework objects are
exposed
+through the standard application, session, and request contexts, where any Java
component in
+the application can make use of them.
+</p>
+
+<p>Markup extensions that use Struts are available for
+<a href="http://jakarta.apache.org/velocity";>Velocity</a> and
+<a href="http://www.openroad.ca/opencode/";>XLST</a>, among others.
+A new Struts tag for
+<a href="#jsf">Java Server Faces</a> is also in development.
+</p>
+
+<p>For more about using WAP/WML with Struts see the article
+<a href="http://www.sys-con.com/pbdj/archives2/0904/hamboeck/";>
+WAP up your EAserver</a>.
+</p>
+</section>
+
<section href="jsf" name="What about the JSTL and JavaServer Faces?">
<p>
The lead developer of Struts, Craig McClanahan, was a member of the
expert group for the JavaServer Standard Tag Library (JSR 052) and
now the specification lead for JavaServer Faces (JSR 127). Both
-technologies are complementary to Struts.
-</p>
+technologies are complementary to Struts.</p>
<p>
The mainstay of the Struts framework is the controller components, which
can be used with any Java presentation technology. As new technologies
become available, it is certain that new "glue" components will also
appear to help these technologies work as well with Struts as the
-bundled JSP tags. This would apply to both the JSTL and JSF.
-</p>
+bundled JSP tags. This would apply to both the JSTL and JSF.</p>
<p>
At some point, we would not be surprised to see Faces become the
preferred UI implementation technology once it is standardized and
available. You can be assured that any future migration will be
made as painless as possible, and maximize your investment in
-Struts.
-</p>
+Struts.</p>
<p>
The JSTL is available through the Jakarta Taglibs site: <br/>
<a
href="http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html";>http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html</a>
@@ -218,6 +241,13 @@
the specification is scheduled for Summer 2002, and an implementation may be
available in Fall of 2002. <a
href="http://servlet.java.sun.com/javaone/sf2002/conf/sessions/display-1697.en.jsp";>
A presentation was given at JavaOne 2002</a> with some additional background.
+</p>
+<p>
+In September 2002, McClanahan announced that a
+<a href="../proposals/struts-faces.html">struts-faces taglib</a> is in
+development and might be released sometime in the Q4 2002. The taglib depends
+on unreleased JSF features, and so an early release of the taglib must follow
+release of a later implementation of JSF.
</p>
</section>
1.4 +27 -1 jakarta-struts/doc/helping.xml
Index: helping.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/helping.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- helping.xml 17 Oct 2002 22:35:55 -0000 1.3
+++ helping.xml 20 Oct 2002 17:06:08 -0000 1.4
@@ -17,9 +17,13 @@
<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>
</ul>
+<p>
+<font face="Arial, Helvetica, sans serif">"You can't always get what you want / but
if you try real hard / you might just find /
+that you get what you need". </font><br/>
+[Rolling Stones]
+</p>
</section>
-
<section href="corp" name="What can my company do to help support Struts?">
<p>Struts is an all volunteer product. Our customers are the volunteers who donate
their time and energy to supporting the product. If you want to support Struts, and
@@ -216,6 +220,28 @@
Committers have more time to spend on the next release. </li>
</ul>
</section>
+
+
+<section href="decisions" name="Who makes the final decisions regarding Struts">
+
+<p>The management of the Jakarta site, and the Struts product, is based on
principles and
+practices used by creators of the Apache HTTPD server. Struts follows the
+<a href="http://jakarta.apache.org/site/guidelines.html";>Project Guidelines</a> on
the
+main Jakarta site.
+</p>
+<p>If you are new to this style of development, the Apache HTTPD Dev list is
available in a
+<a href="[EMAIL PROTECTED]">digest form</a>. Even if you are not
+working on the HTTPD server yourself, it is interesting to watch how the HTTPD team
+works on the server.
+</p>
+<p>The Struts project has its own <a href="index.html#lists">Dev list</a>, where
all of
+the decisions regarding Struts are made. Most development takes place via
+"<a href="http://jakarta.apache.org/site/proposal.html#decisions/voting/items";>Lazy
Consensus</a>".
+Committers post most changes to the product unilaterally, using their own best
judgment,
+and only discuss or vote upon controversial matters. Another Committer can veto any
change in an
+unreleased product with cause.</p>
+</section>
+
<section href="more" name="Other FAQs">
<ul>
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
