Author: buildbot
Date: Sat Nov 22 12:19:40 2014
New Revision: 930095
Log:
Production update by buildbot for tapestry
Modified:
websites/production/tapestry/content/cache/main.pageCache
websites/production/tapestry/content/general-questions.html
websites/production/tapestry/content/release-notes-for-538.html
Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/tapestry/content/general-questions.html
==============================================================================
--- websites/production/tapestry/content/general-questions.html (original)
+++ websites/production/tapestry/content/general-questions.html Sat Nov 22
12:19:40 2014
@@ -48,19 +48,13 @@
</div></div>
<div id="top">
-<div id="smallbanner"><div class="searchbox" style="float:right;margin: .3em
1em .1em 1em">
-<p>
-<span style="color: #999; font-size: 90%">Tapestry docs, issues, wikis &
blogs:</span>
-</p><form enctype="application/x-www-form-urlencoded" method="get"
action="http://tapestry.apache.org/search.html";>
+<div id="smallbanner"><div class="searchbox" style="float:right;margin: .3em
1em .1em 1em"><span style="color: #999; font-size: 90%">Tapestry docs, issues,
wikis & blogs:</span>
+<form enctype="application/x-www-form-urlencoded" method="get"
action="http://tapestry.apache.org/search.html";>
<input type="text" name="q">
<input type="submit" value="Search">
</form>
-</div>
-
-<div class="emblem" style="float:left"><a shape="rect" href="index.html"><img
class="confluence-embedded-image"
src="https://cwiki.apache.org/confluence/download/attachments/21791252/tapestry_s.png?version=3&modificationDate=1293093635000&api=v2";
data-image-src="/confluence/download/attachments/21791252/tapestry_s.png?version=3&modificationDate=1293093635000&api=v2"></a></div>
-<div class="title" style="float:left; margin: 0 0 0 3em">
-<h1 id="SmallBanner-PageTitle">General Questions</h1></div></div>
+</div><div class="emblem" style="float:left"><p><a shape="rect"
href="index.html"><img class="confluence-embedded-image
confluence-external-resource"
src="http://tapestry.apache.org/images/tapestry_small.png";
data-image-src="http://tapestry.apache.org/images/tapestry_small.png";></a></p></div><div
class="title" style="float:left; margin: 0 0 0 3em"><h1
id="SmallBanner-PageTitle">General Questions</h1></div></div>
<div class="clearer"></div>
</div>
@@ -80,65 +74,16 @@ table.ScrollbarTable td.ScrollbarParent
table.ScrollbarTable td.ScrollbarNextName {text-align: right;border: none;}
table.ScrollbarTable td.ScrollbarNextIcon {text-align: center;width:
16px;border: none;}
-/*]]>*/</style><div class="Scrollbar"><table class="ScrollbarTable"><tr><td
colspan="1" rowspan="1" class="ScrollbarPrevName" width="33%"> </td><td
colspan="1" rowspan="1" class="ScrollbarParent" width="33%"><sup><a
shape="rect" href="frequently-asked-questions.html"><img align="middle"
border="0" src="https://cwiki.apache.org/confluence/images/icons/up_16.gif";
width="8" height="8"></a></sup><a shape="rect"
href="frequently-asked-questions.html">Frequently Asked Questions</a></td><td
colspan="1" rowspan="1" class="ScrollbarNextName" width="33%"> <a
shape="rect" href="templating-and-markup-faq.html">Templating and Markup
FAQ</a></td><td colspan="1" rowspan="1" class="ScrollbarNextIcon"><a
shape="rect" href="templating-and-markup-faq.html"><img align="middle"
border="0" src="https://cwiki.apache.org/confluence/images/icons/forwd_16.gif";
width="16" height="16"></a></td></tr></table></div>
-
-<h2 id="GeneralQuestions-GeneralQuestions">General Questions</h2>
-
-<h3 id="GeneralQuestions-HowdoIgetstartedwithTapestry?">How do I get started
with Tapestry?</h3>
-
-<p>The easiest way to get started is to use <a shape="rect"
class="external-link" href="http://maven.apache.org";>Apache Maven</a> to create
your initial project; Maven can use an <em>archetype</em> (a kind of project
template) to create a bare-bones Tapestry application for you. See the <a
shape="rect" href="getting-started.html">Getting Started</a> page for more
details.</p>
-
-<p>Even without Maven, Tapestry is quite easy to set up. You just need to <a
shape="rect" href="download.html">download</a> the binaries and setup your
build to place them inside your WAR's WEB-INF/lib folder. The rest is just some
one-time <a shape="rect" href="configuration.html">configuration of the web.xml
deployment descriptor</a>.</p>
-
-<h3
id="GeneralQuestions-WhydoesTapestryusePrototype?WhynotinsertfavoriteJavaScriptlibraryhere?">Why
does Tapestry use Prototype? Why not <em>insert favorite JavaScript library
here</em>?</h3>
-
-<p>An important goal for Tapestry is seamless DHTML and Ajax integration. To
serve that goal, it was important that the built in components be capable of
Ajax operations, such as dynamically re-rendering parts of the page. Because of
that, it made sense to bundle a well-known JavaScript library as part of
Tapestry.</p>
-
-<p>At the time (this would be 2006-ish), Prototype and Scriptaculous were well
known and well documented, and jQuery was just getting started.</p>
-
-<p>The intent has always been to make this aspect of Tapestry pluggable. Work
is underway to <a shape="rect" href="javascript-rewrite.html">reboot Tapestry's
JavaScript</a> as part of 5.4. This will introduce a modern layer of
modularization, and tease apart the entrenched dependency on Prototype.</p>
-
-<h3
id="GeneralQuestions-WhydoesTapestryhaveitsownInversionofControlContainer?WhynotSpringorGuice?">Why
does Tapestry have its own Inversion of Control Container? Why not Spring or
Guice?</h3>
-
-<p>An Inversion of Control Container is <em>the</em> key piece of Tapestry's
infrastructure. It is absolutely necessary to create software as robust,
performant and extensible as Tapestry.</p>
-
-<p>Tapestry IoC includes a number of features that distinguish itself from
other containers:</p>
-<ul><li>Configured in code, not XML</li><li>Built-in extension mechanism for
services: configurations and contributions</li><li>Built-in aspect oriented
programming model (service decorations and advice)</li><li>Easy
modularization</li><li>Best-of-breed exception reporting</li></ul>
-
-
-<p>Because Tapestry is implemented on top of its IoC container, and because
the container makes it easy to extend or replace any service inside the
container, it is possible to make the small changes to Tapestry needed to
customize it to any project's needs.</p>
-
-<h3 id="GeneralQuestions-HowdoIupgradefromTapestry4toTapestry5?">How do I
upgrade from Tapestry 4 to Tapestry 5?</h3>
-
-<p>There is no existing tool that supports upgrading from Tapestry 4 to
Tapestry 5; Tapestry 5 is a complete rewrite.</p>
-
-<p>Many of the basic concepts in Tapestry 4 are still present in Tapestry 5,
but refactored, improved, streamlined, and simplified. The basic concept of
pages, templates and components are largely the same. Other aspects, such as
server-side event handling, is markedly different.</p>
-
-<h3 id="GeneralQuestions-HowdoIupgradefromoneversionofTapestry5toanother?">How
do I upgrade from one version of Tapestry 5 to another?</h3>
-
-<p>A lot of effort goes into making an upgrade from one Tapestry 5 release to
another go smoothly. In the general case, it is just a matter of updating the
version number in your Maven <code>build.xml</code> or Gradle
<code>build.gradle</code> file and executing the appropriate commands (e.g.,
<code>gradle idea</code> or <code>mvn eclipse:eclipse</code>) to bring your
local workspace up to date with the latest binaries.</p>
-
-<p>After changing dependencies, you should always perform a clean recompile of
your application.</p>
-
-<p>We make every effort to ensure backwards-compatibility. Tapestry is mostly
coded in terms of interfaces; those interfaces are stable to a point:
interfaces your code is expected to implement are usually completely frozen;
interfaces your code is expected to invoke, such as the interfaces to IoC
services, are stable, but may have new methods added in a release; existing
methods are not changed.</p>
-
-<p>In <em>rare</em> cases a choice is necessary between fixing bugs (or
adding essential functionality) and maintaining complete backwards
compatibility; in those cases, an incompatible change may be introduced. These
are always discussed in detail in the <a shape="rect"
href="release-notes.html">Release Notes</a> for the specific release. You
should always read the release notes before attempting an upgrade, and always
(really, <em>always</em>) be prepared to retest your application afterwards.</p>
-
-<p>Note that you should be careful any time you make use of
<strong>internal</strong> APIs (you can tell an API is internal by the package
name, <code>org.apache.tapestry5.internal...</code>. Internal APIs may change
<em>at any time</em>; there's no guarantee of backwards compatibility. Please
always check on the documentation, or consult the user mailing list, to see if
there's a stable, public alternative. If you do make use of internal APIs, be
sure to get a discussion going so that your needs can be met in the future by a
stable, public API.</p>
-
-<p>A final note: Tapestry incorporates your application's version number into
the URLs for JavaScript, CSS, and other assets exposed to the browser; these
assets are cached on the browser with the assumption that when the server-side
assets are changed, the version number (and thus the URL) will change as well.
This version number applies to framework-provided assets as well as those
specific to your application.</p>
-
-<p>Thus, whenever you upgrade, you must change the
<code>tapestry.application-version</code> <a shape="rect"
href="configuration.html">configuration symbol</a> as well. If you fail to do
so, you will see odd behavior in some clients who may be running a mix of old
and new assets. This can result in execution errors or incorrect behavior in
your clients.</p>
-
-<p>Again, after an upgrade to a new version of Tapestry, change your
application version number as well to ensure that the latest version of all
assets are downloaded into your client's browsers.</p>
-
-<h3 id="GeneralQuestions-WhyaretherebothRequestandHttpServletRequest?">Why are
there both Request and HttpServletRequest?</h3>
-
-<p>Tapestry's Request interface is <em>very</em> close to the standard
HttpServletRequest interface. It differs in a few ways, omitting some unneeded
methods, and adding a couple of new methods (such as <code>isXHR()</code>), as
well as changing how some existing methods operate. For example,
<code>getParameterNames()</code> returns a sorted List of Strings;
HttpServletRequest returns an Enumeration, which is a very dated approach.</p>
-
-<p>However, the stronger reason for Request (and the related interfaces
Response and Session) is to enable the support for Portlets at some point in
the future. By writing code in terms of Tapestry's Request, and not
HttpServletRequest, you can be assured that the same code will operate in both
Servlet Tapestry and Portlet Tapestry.</p>
-
-<style type="text/css">/*<![CDATA[*/
+/*]]>*/</style><div class="Scrollbar"><table class="ScrollbarTable"><tr><td
colspan="1" rowspan="1" class="ScrollbarPrevName" width="33%"> </td><td
colspan="1" rowspan="1" class="ScrollbarParent" width="33%"><sup><a
shape="rect" href="frequently-asked-questions.html"><img align="middle"
border="0" src="https://cwiki.apache.org/confluence/images/icons/up_16.gif";
width="8" height="8"></a></sup><a shape="rect"
href="frequently-asked-questions.html">Frequently Asked Questions</a></td><td
colspan="1" rowspan="1" class="ScrollbarNextName" width="33%"> <a
shape="rect" href="templating-and-markup-faq.html">Templating and Markup
FAQ</a></td><td colspan="1" rowspan="1" class="ScrollbarNextIcon"><a
shape="rect" href="templating-and-markup-faq.html"><img align="middle"
border="0" src="https://cwiki.apache.org/confluence/images/icons/forwd_16.gif";
width="16" height="16"></a></td></tr></table></div><h2
id="GeneralQuestions-GeneralQuestions">General Questions</h2><p><style
type="text/css
">/*<![CDATA[*/
+div.rbtoc1416658771961 {padding: 0px;}
+div.rbtoc1416658771961 ul {list-style: disc;margin-left: 0px;}
+div.rbtoc1416658771961 li {margin-left: 0px;padding-left: 0px;}
+
+/*]]>*/</style></p><div class="toc-macro rbtoc1416658771961">
+<ul class="toc-indentation"><li><a shape="rect"
href="#GeneralQuestions-GeneralQuestions">General Questions</a>
+<ul class="toc-indentation"><li><a shape="rect"
href="#GeneralQuestions-HowdoIgetstartedwithTapestry?">How do I get started
with Tapestry?</a></li><li><a shape="rect"
href="#GeneralQuestions-WhydoesTapestryusePrototype?WhynotinsertfavoriteJavaScriptlibraryhere?">Why
does Tapestry use Prototype? Why not insert favorite JavaScript library
here?</a></li><li><a shape="rect"
href="#GeneralQuestions-WhydoesTapestryhaveitsownInversionofControlContainer?WhynotSpringorGuice?">Why
does Tapestry have its own Inversion of Control Container? Why not Spring or
Guice?</a></li><li><a shape="rect"
href="#GeneralQuestions-HowdoIupgradefromTapestry4toTapestry5?">How do I
upgrade from Tapestry 4 to Tapestry 5?</a></li><li><a shape="rect"
href="#GeneralQuestions-HowdoIupgradefromoneversionofTapestry5toanother?">How
do I upgrade from one version of Tapestry 5 to another?</a></li><li><a
shape="rect"
href="#GeneralQuestions-WhyaretherebothRequestandHttpServletRequest?">Why are
there both Request and HttpSe
rvletRequest?</a></li></ul>
+</li></ul>
+</div><h3 id="GeneralQuestions-HowdoIgetstartedwithTapestry?">How do I get
started with Tapestry?</h3><p>The easiest way to get started is to use <a
shape="rect" class="external-link" href="http://maven.apache.org";>Apache
Maven</a> to create your initial project; Maven can use an <em>archetype</em>
(a kind of project template) to create a bare-bones Tapestry application for
you. See the <a shape="rect" href="getting-started.html">Getting Started</a>
page for more details.</p><p>Even without Maven, Tapestry is quite easy to set
up. You just need to <a shape="rect" href="download.html">download</a> the
binaries and setup your build to place them inside your WAR's WEB-INF/lib
folder. The rest is just some one-time <a shape="rect"
href="configuration.html">configuration of the web.xml deployment
descriptor</a>.</p><h3
id="GeneralQuestions-WhydoesTapestryusePrototype?WhynotinsertfavoriteJavaScriptlibraryhere?">Why
does Tapestry use Prototype? Why not <em>insert favorite JavaScript librar
y here</em>?</h3><p>An important goal for Tapestry is seamless DHTML and Ajax
integration. To serve that goal, it was important that the built in components
be capable of Ajax operations, such as dynamically re-rendering parts of the
page. Because of that, it made sense to bundle a well-known JavaScript library
as part of Tapestry.</p><p>At the time (this would be 2006-ish), Prototype and
Scriptaculous were well known and well documented, and jQuery was just getting
started.</p><p>The intent has always been to make this aspect of Tapestry
pluggable. Work is underway to <a shape="rect"
href="javascript-rewrite.html">reboot Tapestry's JavaScript</a> as part of 5.4.
This will introduce a modern layer of modularization, and tease apart the
entrenched dependency on Prototype.</p><h3
id="GeneralQuestions-WhydoesTapestryhaveitsownInversionofControlContainer?WhynotSpringorGuice?">Why
does Tapestry have its own Inversion of Control Container? Why not Spring or
Guice?</h3><p>An Inversion of C
ontrol Container is <em>the</em> key piece of Tapestry's infrastructure. It is
absolutely necessary to create software as robust, performant and extensible as
Tapestry.</p><p>Tapestry IoC includes a number of features that distinguish
itself from other containers:</p><ul><li>Configured in code, not
XML</li><li>Built-in extension mechanism for services: configurations and
contributions</li><li>Built-in aspect oriented programming model (service
decorations and advice)</li><li>Easy modularization</li><li>Best-of-breed
exception reporting</li></ul><p>Because Tapestry is implemented on top of its
IoC container, and because the container makes it easy to extend or replace any
service inside the container, it is possible to make the small changes to
Tapestry needed to customize it to any project's needs.</p><h3
id="GeneralQuestions-HowdoIupgradefromTapestry4toTapestry5?">How do I upgrade
from Tapestry 4 to Tapestry 5?</h3><p>There is no existing tool that supports
upgrading from Tapestry
4 to Tapestry 5; Tapestry 5 is a complete rewrite.</p><p>Many of the basic
concepts in Tapestry 4 are still present in Tapestry 5, but refactored,
improved, streamlined, and simplified. The basic concept of pages, templates
and components are largely the same. Other aspects, such as server-side event
handling, is markedly different.</p><h3
id="GeneralQuestions-HowdoIupgradefromoneversionofTapestry5toanother?">How do I
upgrade from one version of Tapestry 5 to another?</h3><p>A lot of effort goes
into making an upgrade from one Tapestry 5 release to another go smoothly. In
the general case, it is just a matter of updating the version number in your
Maven <code>build.xml</code> or Gradle <code>build.gradle</code> file and
executing the appropriate commands (e.g., <code>gradle idea</code> or <code>mvn
eclipse:eclipse</code>) to bring your local workspace up to date with the
latest binaries.</p><p>After changing dependencies, you should always perform a
clean recompile of your applicati
on.</p><p>We make every effort to ensure backwards-compatibility. Tapestry is
mostly coded in terms of interfaces; those interfaces are stable to a point:
interfaces your code is expected to implement are usually completely frozen;
interfaces your code is expected to invoke, such as the interfaces to IoC
services, are stable, but may have new methods added in a release; existing
methods are not changed.</p><p>In <em>rare</em> cases a choice is necessary
between fixing bugs (or adding essential functionality) and maintaining
complete backwards compatibility; in those cases, an incompatible change may be
introduced. These are always discussed in detail in the <a shape="rect"
href="release-notes.html">Release Notes</a> for the specific release. You
should always read the release notes before attempting an upgrade, and always
(really, <em>always</em>) be prepared to retest your application
afterwards.</p><p>Note that you should be careful any time you make use of
<strong>internal</stron
g> APIs (you can tell an API is internal by the package name,
<code>org.apache.tapestry5.internal...</code>. Internal APIs may change <em>at
any time</em>; there's no guarantee of backwards compatibility. Please always
check on the documentation, or consult the user mailing list, to see if there's
a stable, public alternative. If you do make use of internal APIs, be sure to
get a discussion going so that your needs can be met in the future by a stable,
public API.</p><p>A final note: Tapestry incorporates your application's
version number into the URLs for JavaScript, CSS, and other assets exposed to
the browser; these assets are cached on the browser with the assumption that
when the server-side assets are changed, the version number (and thus the URL)
will change as well. This version number applies to framework-provided assets
as well as those specific to your application.</p><p>Thus, whenever you
upgrade, you must change the <code>tapestry.application-version</code> <a
shape="re
ct" href="configuration.html">configuration symbol</a> as well. If you fail to
do so, you will see odd behavior in some clients who may be running a mix of
old and new assets. This can result in execution errors or incorrect behavior
in your clients.</p><p>Again, after an upgrade to a new version of Tapestry,
change your application version number as well to ensure that the latest
version of all assets are downloaded into your client's browsers.</p><h3
id="GeneralQuestions-WhyaretherebothRequestandHttpServletRequest?">Why are
there both Request and HttpServletRequest?</h3><p>Tapestry's Request interface
is <em>very</em> close to the standard HttpServletRequest interface. It differs
in a few ways, omitting some unneeded methods, and adding a couple of new
methods (such as <code>isXHR()</code>), as well as changing how some existing
methods operate. For example, <code>getParameterNames()</code> returns a sorted
List of Strings; HttpServletRequest returns an Enumeration, which is a ver
y dated approach.</p><p>However, the stronger reason for Request (and the
related interfaces Response and Session) is to enable the support for Portlets
at some point in the future. By writing code in terms of Tapestry's Request,
and not HttpServletRequest, you can be assured that the same code will operate
in both Servlet Tapestry and Portlet Tapestry.</p><style
type="text/css">/*<![CDATA[*/
table.ScrollbarTable {border: none;padding: 3px;width: 100%;padding:
3px;margin: 0px;background-color: #f0f0f0}
table.ScrollbarTable td.ScrollbarPrevIcon {text-align: center;width:
16px;border: none;}
table.ScrollbarTable td.ScrollbarPrevName {text-align: left;border: none;}
Modified: websites/production/tapestry/content/release-notes-for-538.html
==============================================================================
--- websites/production/tapestry/content/release-notes-for-538.html (original)
+++ websites/production/tapestry/content/release-notes-for-538.html Sat Nov 22
12:19:40 2014
@@ -56,7 +56,7 @@
</div>
<div id="content">
-<div id="ConfluenceContent"><p>Tapestry 5.3.8 is a drop-in replacement for
prior Tapestry 5.3 releases. To upgrade, just update the Maven dependency in
your POM file (or <a shape="rect"
href="https://cwiki.apache.org/confluence/display/TAPESTRY/Download";>download</a>
the new JAR file) and the new version will just work. However, please review
the <a shape="rect"
href="https://cwiki.apache.org/confluence/display/TAPESTRY/How+to+Upgrade";>How
to Upgrade</a> instructions before upgrading.</p><p>This is a bug fix release,
mainly meant to address compatibility with Java 8.</p><p>As with any Tapestry
upgrade, be sure to change your <a shape="rect"
href="https://cwiki.apache.org/confluence/display/TAPESTRY/General+Questions";>application's
version number</a>.</p><p> </p>
+<div id="ConfluenceContent"><p>Tapestry 5.3.8 is a drop-in replacement for
prior Tapestry 5.3 releases. To upgrade, just update the dependency in your
build configuration (Maven POM, Gradle build script, etc.) – or <a
shape="rect"
href="https://cwiki.apache.org/confluence/display/TAPESTRY/Download";>download</a>
the new JAR file -- and the new version will just work. However, please review
the <a shape="rect"
href="https://cwiki.apache.org/confluence/display/TAPESTRY/How+to+Upgrade";>How
to Upgrade</a> instructions before upgrading.</p><p>This is a bug fix release,
mainly meant to address compatibility with Java 8.</p><p>As with any Tapestry
upgrade, be sure to change your <a shape="rect"
href="https://cwiki.apache.org/confluence/display/TAPESTRY/General+Questions";>application's
version number</a>.</p><p> </p>
<h2> Bugs fixed
</h2>
<ul><li>[<a shape="rect"
href="https://issues.apache.org/jira/browse/TAP5-311";>TAP5-311</a>] -
NPE in BeanDisplay if used in a form with a default model
![https://cwiki.apache.org/confluence/download/attachments/21791252/tapestry_s.png?version=3&modificationDate=1293093635000&api=v2"](https://cwiki.apache.org/confluence/download/attachments/21791252/tapestry_s.png?version=3&modificationDate=1293093635000&api=v2"){kind=link}
![http://tapestry.apache.org/images/tapestry_small.png"](http://tapestry.apache.org/images/tapestry_small.png"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/up_16.gif"](https://cwiki.apache.org/confluence/images/icons/up_16.gif"){kind=link}
![https://cwiki.apache.org/confluence/images/icons/forwd_16.gif"](https://cwiki.apache.org/confluence/images/icons/forwd_16.gif"){kind=link}