You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by ad...@apache.org on 2014/04/26 22:03:30 UTC
svn commit: r1590290 [9/10] - in /wicket/common/site/trunk: ./ _posts/
_site/ _site/2009/07/30/ _site/2009/08/21/ _site/2009/10/12/
_site/2009/10/24/ _site/2009/12/13/ _site/2009/12/21/ _site/2010/02/01/
_site/2010/03/05/ _site/2010/05/03/ _site/2010/0...
Modified: wicket/common/site/trunk/_site/learn/ides.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/ides.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/ides.html (original)
+++ wicket/common/site/trunk/_site/learn/ides.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,28 +174,28 @@
<div id="contentbody">
<h1>IDE Support for Wicket development</h1>
- <h2 id="wicket_plugins">Wicket Plugins</h2>
+ <h2 id='wicket_plugins'>Wicket Plugins</h2>
-<p>For all leading IDEâs support is under development. Hereâs a list of efforts for the major IDEâs.</p>
+<p>For all leading IDE’s support is under development. Here’s a list of efforts for the major IDE’s.</p>
<ul>
-<li>Eclipse: <a href="http://code.google.com/p/qwickie">Qwickie</a>, <a href="https://github.com/42Lines/wicket-source/wiki">Wicket Source</a></li>
+<li>Eclipse: <a href='http://code.google.com/p/qwickie'>Qwickie</a>, <a href='https://github.com/42Lines/wicket-source/wiki'>Wicket Source</a></li>
-<li>Netbeans: <a href="https://nbwicketsupport.dev.java.net/">NB Wicket Support</a></li>
+<li>Netbeans: <a href='https://nbwicketsupport.dev.java.net/'>NB Wicket Support</a></li>
-<li>IntelliJ IDEA: <a href="http://wicketforge.googlecode.com/">Wicket Forge</a>, <a href="https://github.com/armhold/wicket-source-intellij">Wicket Source</a></li>
+<li>IntelliJ IDEA: <a href='http://wicketforge.googlecode.com/'>Wicket Forge</a>, <a href='https://github.com/armhold/wicket-source-intellij'>Wicket Source</a></li>
</ul>
<p>These projects are not maintained or supported by the core Wicket team, but by their respective development teams.</p>
-<h2 id="setting_up_your_ide">Setting up your IDE</h2>
+<h2 id='setting_up_your_ide'>Setting up your IDE</h2>
-<h3 id="eclipse">Eclipse</h3>
+<h3 id='eclipse'>Eclipse</h3>
<p>Taking Maven, project configuration files for Eclipse can be generated with:</p>
<div class='highlight'><pre><code class='console'><span class='go'>mvn eclipse:eclipse</span>
</code></pre></div>
-<p>Maven will add all the necessary JAR files to the projectâs classpath. Now the sources can be imported in Eclipse using the âExisting Projects into Workspaceâ wizard.</p>
+<p>Maven will add all the necessary JAR files to the project’s classpath. Now the sources can be imported in Eclipse using the “Existing Projects into Workspace” wizard.</p>
<p>If not already present the <code>M2_REPO</code> classpath variable has to point to your local Maven repository. The repository is typically found in <code>C:\Documents and Settings\<username>\.m2\repo</code> or (for unix buffs) <code>~/.m2/repo</code>. It can be set within Eclipse (Preferences->Java->Build Path->Classpath Variables) or with the help of Maven:</p>
<div class='highlight'><pre><code class='console'><span class='go'>mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo</span>
@@ -205,15 +205,15 @@
</code></pre></div>
<p>Finally configure the editor to automatically format all edited lines and organize imports on save (Preferences->Java->Editor->Save Actions).</p>
-<h3 id="netbeans">NetBeans</h3>
+<h3 id='netbeans'>NetBeans</h3>
-<p>NetBeans comes with Maven integration. Further help can be found at their <a href="http://wiki.netbeans.org/MavenBestPractices" title="NetBeans Community Wiki">Wiki</a></p>
+<p>NetBeans comes with Maven integration. Further help can be found at their <a href='http://wiki.netbeans.org/MavenBestPractices' title='NetBeans Community Wiki'>Wiki</a></p>
-<h3 id="idea">IDEA</h3>
+<h3 id='idea'>IDEA</h3>
-<p>IntelliJ IDEA comes with <a href="http://www.jetbrains.com/idea/webhelp/maven.html" title="IDEA Web Help">Maven support</a> too.</p>
+<p>IntelliJ IDEA comes with <a href='http://www.jetbrains.com/idea/webhelp/maven.html' title='IDEA Web Help'>Maven support</a> too.</p>
-<p>With the <a href="http://plugins.jetbrains.com/plugin/6546">Eclipse Code Formatter plugin</a> the Wicket format profile can be used in IntelliJ IDEA too. Configure the IDE to prevent star imports (Settings->Code Style->Imports).</p>
+<p>With the <a href='http://plugins.jetbrains.com/plugin/6546'>Eclipse Code Formatter plugin</a> the Wicket format profile can be used in IntelliJ IDEA too. Configure the IDE to prevent star imports (Settings->Code Style->Imports).</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/index.html (original)
+++ wicket/common/site/trunk/_site/learn/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
Modified: wicket/common/site/trunk/_site/learn/projects/authroles.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/authroles.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/authroles.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/authroles.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -176,43 +176,43 @@
<h1>Wicket Auth/Roles</h1>
<p>This is mostly a technology demonstration implementing authorization and authentication for the Apache Wicket web framework. The project supplies roles based authorization and some simple authentication components.</p>
-<h2 id="contents">Contents</h2>
+<h2 id='contents'>Contents</h2>
<ul>
-<li><a href="#introduction">Introduction</a></li>
+<li><a href='#introduction'>Introduction</a></li>
-<li><a href="#example">Example</a></li>
+<li><a href='#example'>Example</a></li>
-<li><a href="#installing">Installing</a></li>
+<li><a href='#installing'>Installing</a></li>
</ul>
-<h2 id="introduction">Introduction</h2>
+<h2 id='introduction'>Introduction</h2>
-<p>Wicket Auth/Roles is a simplistic but useful security extension to the Wicket framework. It is intended to be simplistic and not to be confused with a framework. If you find this library useful, great. If you need more than is supplied by this library, either look at <a href="#alternatives">alternative security integrations</a> or copy these classes and modify them at will (this project <strong>is</strong> <a href="http://www.apache.org/licenses/">open source</a> after all.)</p>
+<p>Wicket Auth/Roles is a simplistic but useful security extension to the Wicket framework. It is intended to be simplistic and not to be confused with a framework. If you find this library useful, great. If you need more than is supplied by this library, either look at <a href='#alternatives'>alternative security integrations</a> or copy these classes and modify them at will (this project <strong>is</strong> <a href='http://www.apache.org/licenses/'>open source</a> after all.)</p>
-<p>Like most if not all security solutions for Wicket, this project provides an implementation for Wicketâs <code>IAuthorizationStrategy</code>. When an authorization strategy is installed in the security settings (<code>WebApplication#getSecuritySettings</code>), Wicket will check for each component (including pages) if instantiation is allowed and if rendering is allowed.</p>
+<p>Like most if not all security solutions for Wicket, this project provides an implementation for Wicket’s <code>IAuthorizationStrategy</code>. When an authorization strategy is installed in the security settings (<code>WebApplication#getSecuritySettings</code>), Wicket will check for each component (including pages) if instantiation is allowed and if rendering is allowed.</p>
<p>For more documentation use the following links:</p>
<ul>
-<li><a href="http://wicket.apache.org/apidocs/1.5/org/apache/wicket/authentication/package-summary.html">Authentication API</a></li>
+<li><a href='http://wicket.apache.org/apidocs/1.5/org/apache/wicket/authentication/package-summary.html'>Authentication API</a></li>
-<li><a href="http://wicket.apache.org/apidocs/1.5/org/apache/wicket/authorization/package-summary.html">Authorization API</a></li>
+<li><a href='http://wicket.apache.org/apidocs/1.5/org/apache/wicket/authorization/package-summary.html'>Authorization API</a></li>
</ul>
<p>Note that for the instantiation check Wicket will invoke the constructor hierarchy of your component, but will throw an exception if the authorization check fails.</p>
-<h3 id="authentication">Authentication</h3>
+<h3 id='authentication'>Authentication</h3>
-<p>As a basis, you should extend your web application class from <code>AuthenticatedWebApplication</code>. When you create your class youâll be asked to override the following methods:</p>
+<p>As a basis, you should extend your web application class from <code>AuthenticatedWebApplication</code>. When you create your class you’ll be asked to override the following methods:</p>
<ul>
<li><code>newSession</code> - return a subclass of <code>AuthenticatedWebSession</code></li>
-<li><code>getSignInPageClass</code> - return the class for your login page (this one should not require authentication, otherwise youâll create an infinite loop)</li>
+<li><code>getSignInPageClass</code> - return the class for your login page (this one should not require authentication, otherwise you’ll create an infinite loop)</li>
</ul>
-<p>Next youâll need to provide your custom session class-making it a subclass of <code>AuthenticatedWebSession</code>. This class requires you to override the following methods:</p>
+<p>Next you’ll need to provide your custom session class-making it a subclass of <code>AuthenticatedWebSession</code>. This class requires you to override the following methods:</p>
<ul>
<li><code>authenticate</code> - called when the user needs to be authenticated using a username and password</li>
@@ -220,9 +220,9 @@
<li><code>getRoles</code> - called after the users was authenticated and should provide the roles associated with the authenticated user.</li>
</ul>
-<p>You can use the provided <code>SignInPage</code>, which has been translated to a couple of languages (see the source code for the actual translations), or roll your own. When you roll your own, you can opt to use the provided <code>SignInPanel</code> (which has been translated as well) so you donât have to create your own login form.</p>
+<p>You can use the provided <code>SignInPage</code>, which has been translated to a couple of languages (see the source code for the actual translations), or roll your own. When you roll your own, you can opt to use the provided <code>SignInPanel</code> (which has been translated as well) so you don’t have to create your own login form.</p>
-<h3 id="authorization">Authorization</h3>
+<h3 id='authorization'>Authorization</h3>
<p>Annotation for configuring what roles are allowed for instantiation the annotated component or package. This annotation can be used for classes and packages, and can be used like this:</p>
<div class='highlight'><pre><code class='java'><span class='c1'>// only users with role ADMIN are allowed to create instances of this page, whether it is</span>
@@ -230,46 +230,42 @@
<span class='nd'>@AuthorizeInstantiation</span><span class='o'>(</span><span class='s'>"ADMIN"</span><span class='o'>)</span>
<span class='kd'>public</span> <span class='kd'>class</span> <span class='nc'>AdminAnnotationsBookmarkablePage</span> <span class='kd'>extends</span> <span class='n'>WebPage</span>
</code></pre></div>
-<p>When someone who doesnât have the role ADMIN, Wicket will not allow the page to be fully constructed and throw an authorization exception during the construction of the page. This will result in an access denied page for the user.</p>
+<p>When someone who doesn’t have the role ADMIN, Wicket will not allow the page to be fully constructed and throw an authorization exception during the construction of the page. This will result in an access denied page for the user.</p>
<p>Enablng the annotations for role based authorization is done by setting the <code>WebApplication#getSecuritySettings</code> value to <code>AnnotationsRoleAuthorizationStrategy</code>. Then you can use the auth/roles provided authorization annotations.</p>
-<h3 id="alternatives">Alternatives</h3>
+<h3 id='alternatives'>Alternatives</h3>
<p>More elaborate security solutions exist in the following projects:</p>
<ul>
-<li><a href="https://github.com/wicketstuff/core/tree/core-1.5.x/jdk-1.5-parent/shiro-security">Wicket Shiro</a> - integration between Apache Shiro and Wicket</li>
+<li><a href='https://github.com/wicketstuff/core/tree/core-1.5.x/jdk-1.5-parent/shiro-security'>Wicket Shiro</a> - integration between Apache Shiro and Wicket</li>
-<li><a href="https://github.com/wicketstuff/core/tree/core-1.5.x/jdk-1.5-parent/wicket-security-parent">Wicket Security</a>
-<ul>
-<li>JAAS inspired, principal based security framework</li>
-</ul>
-</li>
+<li><a href='https://github.com/wicketstuff/core/tree/core-1.5.x/jdk-1.5-parent/wicket-security-parent'>Wicket Security</a> - JAAS inspired, principal based security framework</li>
</ul>
-<p>If other security solutions are available for Wicket, <a href="https://issues.apache.org/jira/browse/WICKET">let us know</a>.</p>
+<p>If other security solutions are available for Wicket, <a href='https://issues.apache.org/jira/browse/WICKET'>let us know</a>.</p>
-<h2 id="example">Example</h2>
+<h2 id='example'>Example</h2>
-<p>The Wicket Examples project contains a <a href="http://wicket-library.com/wicket-examples/authorization">complete example</a> of limiting access to pages and components using roles based authorization. It also contains an <a href="http://wicket-library.com/wicket-examples/authentication">authentication example</a>.</p>
+<p>The Wicket Examples project contains a <a href='http://wicket-library.com/wicket-examples/authorization'>complete example</a> of limiting access to pages and components using roles based authorization. It also contains an <a href='http://wicket-library.com/wicket-examples/authentication'>authentication example</a>.</p>
<p>Click on the source links to see the related source code.</p>
-<h2 id="installing">Installing</h2>
+<h2 id='installing'>Installing</h2>
-<p>Installing Wicket Auth/Roles can be done through adding a dependency in your projectâs Maven pom, or by putting the wicket-auth-roles.jar and the required dependencies in your projects classpath.</p>
+<p>Installing Wicket Auth/Roles can be done through adding a dependency in your project’s Maven pom, or by putting the wicket-auth-roles.jar and the required dependencies in your projects classpath.</p>
-<h3 id="using_maven">Using Maven</h3>
+<h3 id='using_maven'>Using Maven</h3>
<p>Add the following dependency to your pom:</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span>
<span class='nt'><groupId></span>org.apache.wicket<span class='nt'></groupId></span>
<span class='nt'><artifactId></span>wicket-auth-roles<span class='nt'></artifactId></span>
- <span class='nt'><version></span>6.14.0<span class='nt'></version></span>
+ <span class='nt'><version></span>6.15.0<span class='nt'></version></span>
<span class='nt'></dependency></span>
</code></pre></div>
-<h3 id="required_dependencies">Required dependencies</h3>
+<h3 id='required_dependencies'>Required dependencies</h3>
<p>Wicket Auth/Roles requires the following jar files to be on your classpath:</p>
Modified: wicket/common/site/trunk/_site/learn/projects/datetime.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/datetime.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/datetime.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/datetime.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket Date/Time</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/devutils.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/devutils.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/devutils.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/devutils.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket Dev Utils</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/extensions.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/extensions.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/extensions.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/extensions.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket Extensions</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/guice.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/guice.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/guice.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/guice.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket Guice</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/index.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -178,42 +178,42 @@
<ul>
<li>
-<p><a href="authroles.html">Wicket Auth/Roles</a> - very basic security project enabling annotation based authorization for two roles: user and admin.</p>
+<p><a href='authroles.html'>Wicket Auth/Roles</a> - very basic security project enabling annotation based authorization for two roles: user and admin.</p>
</li>
<li>
-<p><a href="datetime.html">Wicket Date/Time</a> - date components</p>
+<p><a href='datetime.html'>Wicket Date/Time</a> - date components</p>
</li>
<li>
-<p><a href="devutils.html">Wicket Dev Utils</a> - utilities that improve developer productivity by opening up the internals of your Wicket application right inside the web UI.</p>
+<p><a href='devutils.html'>Wicket Dev Utils</a> - utilities that improve developer productivity by opening up the internals of your Wicket application right inside the web UI.</p>
</li>
<li>
-<p><a href="extensions.html">Wicket Extensions</a> - additional components that are beyond the scope of the core Wicket framework. Contains components such as DataTable, MultiFileUpload, Rating component</p>
+<p><a href='extensions.html'>Wicket Extensions</a> - additional components that are beyond the scope of the core Wicket framework. Contains components such as DataTable, MultiFileUpload, Rating component</p>
</li>
<li>
-<p><a href="jmx.html">Wicket JMX</a> - opens up the internals of Wicket through JMX beans</p>
+<p><a href='jmx.html'>Wicket JMX</a> - opens up the internals of Wicket through JMX beans</p>
</li>
<li>
-<p><a href="ioc.html">Wicket IoC</a> - base services for the Guice and Spring integrations</p>
+<p><a href='ioc.html'>Wicket IoC</a> - base services for the Guice and Spring integrations</p>
</li>
<li>
-<p><a href="guice.html">Wicket integration for Guice</a> - inject <a href="http://code.google.com/p/google-guice">Guice</a> managed services in a Wicket compatible manner</p>
+<p><a href='guice.html'>Wicket integration for Guice</a> - inject <a href='http://code.google.com/p/google-guice'>Guice</a> managed services in a Wicket compatible manner</p>
</li>
<li>
-<p><a href="spring.html">Wicket integration for Spring</a> - inject <a href="http://springsource.org">Spring</a> managed services in a Wicket compatible manner</p>
+<p><a href='spring.html'>Wicket integration for Spring</a> - inject <a href='http://springsource.org'>Spring</a> managed services in a Wicket compatible manner</p>
</li>
</ul>
-<h2 id="integrations_with_other_template_engines">Integrations with other template engines</h2>
+<h2 id='integrations_with_other_template_engines'>Integrations with other template engines</h2>
<ul>
-<li><a href="velocity.html">Wicket integration for Apache Velocity</a> - use <a href="http://velocity.apache.org">Velocity</a> templates in your Wicket application</li>
+<li><a href='velocity.html'>Wicket integration for Apache Velocity</a> - use <a href='http://velocity.apache.org'>Velocity</a> templates in your Wicket application</li>
</ul>
</div>
<div id="clearer"></div>
Modified: wicket/common/site/trunk/_site/learn/projects/ioc.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/ioc.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/ioc.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/ioc.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket IoC</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/jmx.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/jmx.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/jmx.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/jmx.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket JMX</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/spring.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/spring.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/spring.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/spring.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,7 +174,7 @@
<div id="contentbody">
<h1>Wicket Spring</h1>
- <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href="velocity.html">Velocity project description</a>.</p>
+ <p>Waiting for someone to contribute some introductory documentation about this project. See for an example the <a href='velocity.html'>Velocity project description</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/projects/velocity.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/projects/velocity.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/velocity.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/velocity.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,19 +174,19 @@
<div id="contentbody">
<h1>Wicket Velocity</h1>
- <p>Provides a specialized panel and some related utilities that enables users to work with <a href="http://velocity.apache.org">Apache Velocity</a> and <a href="http://wicket.apache.org">Apache Wicket</a>. Particularly useful for simple CMS like applications.</p>
+ <p>Provides a specialized panel and some related utilities that enables users to work with <a href='http://velocity.apache.org'>Apache Velocity</a> and <a href='http://wicket.apache.org'>Apache Wicket</a>. Particularly useful for simple CMS like applications.</p>
-<h2 id="contents">Contents</h2>
+<h2 id='contents'>Contents</h2>
<ul>
-<li><a href="#introduction">Introduction</a></li>
+<li><a href='#introduction'>Introduction</a></li>
-<li><a href="#example">Example</a></li>
+<li><a href='#example'>Example</a></li>
-<li><a href="#installing">Installing</a></li>
+<li><a href='#installing'>Installing</a></li>
</ul>
-<h2 id="introduction">Introduction</h2>
+<h2 id='introduction'>Introduction</h2>
<p>Velocity brings a templating language to your users. You can let them create conditional markup, use loops and do all other things made possible by Velocity.</p>
@@ -200,20 +200,20 @@
They are not equivalent and this will be the output.
#end
</code></pre></div>
-<p>Read <a href="http://velocity.apache.org/engine/releases/velocity-1.4/user-guide.html">more</a> about the Velocity template language.</p>
+<p>Read <a href='http://velocity.apache.org/engine/releases/velocity-1.4/user-guide.html'>more</a> about the Velocity template language.</p>
<p>This project allows you to use Velocity templates as a component within your Wicket pages, and let them live next to Wicket components. A typical usecase would be to enable your users to embed Velocity templates in your application and using that as a type of portlet.</p>
-<p>The main component for the Veloticy/Wicket integration is the <a href="http://wicket.apache.org/docs/1.4/org/apache/wicket/velocity/markup/html/VelocityPanel.html"><code>VelocityPanel</code></a>.</p>
+<p>The main component for the Veloticy/Wicket integration is the <a href='http://wicket.apache.org/docs/1.4/org/apache/wicket/velocity/markup/html/VelocityPanel.html'><code>VelocityPanel</code></a>.</p>
-<h2 id="example">Example</h2>
+<h2 id='example'>Example</h2>
<p>Showing Hello, World using Velocity in a Wicket application, embedded in a Wicket page.</p>
<div class='highlight'><pre><code class='html'><span class='nt'><h2></span>This is a Velocity template<span class='nt'></h2></span>
<span class='nt'><p></span>The secret message is: $message<span class='nt'></p></span>
</code></pre></div>
-<p>In this template we want to replace the string <code>$message</code> with the text âHello, World!â. <code>$message</code> is Velocity markup denoting a variable that is taken from the context that is provided to the Velocity rendering engine.</p>
+<p>In this template we want to replace the string <code>$message</code> with the text “Hello, World!”. <code>$message</code> is Velocity markup denoting a variable that is taken from the context that is provided to the Velocity rendering engine.</p>
<p>To use Velocity in your Wicket pages we provide a <code>VelocityPanel</code> which enables you to generate parts of your page using Velocity markup. Adding the panel to your Wicket page is shown in the following example:</p>
<div class='highlight'><pre><code class='java'><span class='kd'>public</span> <span class='nf'>VelocityPage</span><span class='o'>()</span> <span class='o'>{</span>
@@ -232,20 +232,20 @@
<span class='nt'><h1></span>This is a test page for Velocity<span class='nt'></h1></span>
<span class='nt'><div</span> <span class='na'>wicket:id=</span><span class='s'>"velocityPanel"</span><span class='nt'>></div></span>
</code></pre></div>
-<h2 id="installing">Installing</h2>
+<h2 id='installing'>Installing</h2>
-<p>Installing Wicket Velocity can be done through adding a dependency in your projectâs Maven pom, or by putting the wicket-velocity.jar and the required dependencies in your projects classpath.</p>
+<p>Installing Wicket Velocity can be done through adding a dependency in your project’s Maven pom, or by putting the wicket-velocity.jar and the required dependencies in your projects classpath.</p>
-<h3 id="using_maven">Using Maven</h3>
+<h3 id='using_maven'>Using Maven</h3>
<p>Add the following dependency to your pom:</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span>
<span class='nt'><groupId></span>org.apache.wicket<span class='nt'></groupId></span>
<span class='nt'><artifactId></span>wicket-velocity<span class='nt'></artifactId></span>
- <span class='nt'><version></span>6.14.0<span class='nt'></version></span>
+ <span class='nt'><version></span>6.15.0<span class='nt'></version></span>
<span class='nt'></dependency></span>
</code></pre></div>
-<h3 id="required_dependencies">Required dependencies</h3>
+<h3 id='required_dependencies'>Required dependencies</h3>
<p>Wicket Velocity requires the following jar files to be on your classpath:</p>
@@ -257,7 +257,7 @@
<li>Apache Velocity</li>
</ul>
-<p>Check the <a href="http://velocity.apache.org">Apache Velocity project</a> to find out which other dependencies you need.</p>
+<p>Check the <a href='http://velocity.apache.org'>Apache Velocity project</a> to find out which other dependencies you need.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/meet/blogs.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/blogs.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/blogs.html (original)
+++ wicket/common/site/trunk/_site/meet/blogs.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -179,38 +179,38 @@
<p>Here is a list of regular Wicket bloggers, consisting of core contributers and enthusiastic users.</p>
<ul>
-<li><a href="http://wicketinaction.com/">Wicket in Action</a> - Igor Vaynberg, Martijn Dashorst</li>
+<li><a href='http://wicketinaction.com/'>Wicket in Action</a> - Igor Vaynberg, Martijn Dashorst</li>
-<li><a href="http://chillenious.wordpress.com/">Chillenious!</a> - Eelco Hillenius</li>
+<li><a href='http://chillenious.wordpress.com/'>Chillenious!</a> - Eelco Hillenius</li>
-<li><a href="http://codeact.wordpress.com/">Jonathan</a> - Jonathan Locke</li>
+<li><a href='http://codeact.wordpress.com/'>Jonathan</a> - Jonathan Locke</li>
-<li><a href="http://herebebeasties.com/">Here be beasties</a> - Al Maw</li>
+<li><a href='http://herebebeasties.com/'>Here be beasties</a> - Al Maw</li>
-<li><a href="http://www.jeremythomerson.com/blog">Jeremy Thomerson</a> - Jeremy Thomerson</li>
+<li><a href='http://www.jeremythomerson.com/blog'>Jeremy Thomerson</a> - Jeremy Thomerson</li>
-<li><a href="http://technically.us/code">Codierspiel</a> - Nathan Hamblen (runs on Wicket)</li>
+<li><a href='http://technically.us/code'>Codierspiel</a> - Nathan Hamblen (runs on Wicket)</li>
-<li><a href="http://www.antwerkz.com/wp/">Antwerkz</a> - Justin Lee</li>
+<li><a href='http://www.antwerkz.com/wp/'>Antwerkz</a> - Justin Lee</li>
-<li><a href="http://www.systemmobile.com/?cat=4">System Mobile</a> - Nick Heudecker</li>
+<li><a href='http://www.systemmobile.com/?cat=4'>System Mobile</a> - Nick Heudecker</li>
-<li><a href="http://blogs.sun.com/geertjan">Geertjan</a> - Geertjan Wielenga</li>
+<li><a href='http://blogs.sun.com/geertjan'>Geertjan</a> - Geertjan Wielenga</li>
-<li><a href="http://martijndashorst.com/blog">A Wicket Diary</a> - Martijn Dashorst</li>
+<li><a href='http://martijndashorst.com/blog'>A Wicket Diary</a> - Martijn Dashorst</li>
-<li><a href="http://www.wicket-praxis.de/blog/">Wicket Praxis</a> - Michael Mosmann</li>
+<li><a href='http://www.wicket-praxis.de/blog/'>Wicket Praxis</a> - Michael Mosmann</li>
-<li><a href="http://mysticcoders.com/blog">Mystic Coders</a> - Andrew Lombardi</li>
+<li><a href='http://mysticcoders.com/blog'>Mystic Coders</a> - Andrew Lombardi</li>
-<li><a href="http://wicketbyexample.com/">Wicket by Example</a> - Community driven</li>
+<li><a href='http://wicketbyexample.com/'>Wicket by Example</a> - Community driven</li>
-<li><a href="http://yeswicket.com/">Yes Wicket!</a> - French Wicket blog</li>
+<li><a href='http://yeswicket.com/'>Yes Wicket!</a> - French Wicket blog</li>
</ul>
-<h2 id="get_your_blog_listed">Get your blog listed!</h2>
+<h2 id='get_your_blog_listed'>Get your blog listed!</h2>
-<p>If you think your blog is missing, then please send a message to one of the core contributors or the mailinglist. In the mean time you can add your blog to our wikiâs <a href="https://cwiki.apache.org/confluence/display/WICKET/Wicket+Blogs">special blog page</a>.</p>
+<p>If you think your blog is missing, then please send a message to one of the core contributors or the mailinglist. In the mean time you can add your blog to our wiki’s <a href='https://cwiki.apache.org/confluence/display/WICKET/Wicket+Blogs'>special blog page</a>.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/meet/buzz.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/buzz.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/buzz.html (original)
+++ wicket/common/site/trunk/_site/meet/buzz.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -177,79 +177,79 @@
<p>Wicket has appeared in the press in a variety of industry trade magazines, including Network World, ComputerWorld, IT World and Information Week. Presentations on Wicket have been delivered by Wicket team members at JavaOne in San Francisco, Javapolis and TheServerSide Java Symposium in Europe. The following are quotes from reviewers and users of Wicket:</p>
<blockquote>
-<p>After working with JSF for almost a year, trying Wicket was like that movie scene where the clouds part and this big ray of light hits you in the face. I just had this feeling while JSFâing that certain things were harder than they needed to be. Well, I was right, and the Wicket people figured it out.</p>
+<p>After working with JSF for almost a year, trying Wicket was like that movie scene where the clouds part and this big ray of light hits you in the face. I just had this feeling while JSF’ing that certain things were harder than they needed to be. Well, I was right, and the Wicket people figured it out.</p>
-<p><a href="http://bigheadco.blogspot.com/2007/03/groovy-wicket.html">Kevin Galligan</a></p>
+<p><a href='http://bigheadco.blogspot.com/2007/03/groovy-wicket.html'>Kevin Galligan</a></p>
</blockquote>
<blockquote>
<p>Wicket (currently undergoing incubation with Apache) is a good example of a web framework which throws caution to the wind, and has absolutely no XML needed. We here at Mystic have a lot of love for Wicket and are actively developing several projects with it currently.</p>
-<p><a href="http://www.mysticcoders.com/blog/2007/03/13/the-rise-of-the-xml-backlash/">Mystic Coders</a></p>
+<p><a href='http://www.mysticcoders.com/blog/2007/03/13/the-rise-of-the-xml-backlash/'>Mystic Coders</a></p>
</blockquote>
<blockquote>
<p>Writing a Wicket app is rather more like writing an event-based desktop application than a web application.</p>
-<p><a href="http://www.lshift.net/blog/2006/07/06/wicket">LShift</a></p>
+<p><a href='http://www.lshift.net/blog/2006/07/06/wicket'>LShift</a></p>
</blockquote>
<blockquote>
-<p>âWickedly Coolâ - I actually managed to whip together a Wicket Application in a few days. It is entertaining to work with, adding shiny stuff is really easy while you can develop Java code and keep those last bits of hair you have saved for ripping out in a CSS nightmare that you hopefully after finding Wicket will not have to deal with. So Iâd go out on a limb and say that Wicket == Rogaine for developers.</p>
+<p>“Wickedly Cool” - I actually managed to whip together a Wicket Application in a few days. It is entertaining to work with, adding shiny stuff is really easy while you can develop Java code and keep those last bits of hair you have saved for ripping out in a CSS nightmare that you hopefully after finding Wicket will not have to deal with. So I’d go out on a limb and say that Wicket == Rogaine for developers.</p>
-<p><a href="http://blogs.opennms.org/joed/?p=3">Joed</a></p>
+<p><a href='http://blogs.opennms.org/joed/?p=3'>Joed</a></p>
</blockquote>
<blockquote>
-<p>âSo is Wicket the one true MVC framework that a lot of us have been hunting for? At the moment, I tend to think so. [â¦] If you like Java you will really like Wicket.â</p>
+<p>“So is Wicket the one true MVC framework that a lot of us have been hunting for? At the moment, I tend to think so. […] If you like Java you will really like Wicket.”</p>
-<p><a href="http://ptrthomas.wordpress.com/2007/03/02/wicket-impressions-moving-from-spring-mvc-webflow/">Peter Thomas</a></p>
+<p><a href='http://ptrthomas.wordpress.com/2007/03/02/wicket-impressions-moving-from-spring-mvc-webflow/'>Peter Thomas</a></p>
</blockquote>
<blockquote>
-<p>âI think its an awesome way to deal with this whole web UI framework mess. I am happy to see someone take a simple and clean approach to the whole problem, and come up with a transparent POJO solution. I like the direction the framework is going⦠Wicket is clean, simple and elegant.â</p>
+<p>“I think its an awesome way to deal with this whole web UI framework mess. I am happy to see someone take a simple and clean approach to the whole problem, and come up with a transparent POJO solution. I like the direction the framework is going… Wicket is clean, simple and elegant.”</p>
<p>Comment on TheServerSide.com</p>
</blockquote>
<blockquote>
-<p>âLast week I wrote an article about Wicket and I spent some time discovering and taming it. And I have to confess this: I love it. ⦠snip ⦠Wicket is not a framework, itâs a candy bar. And everybody loves candy barsâ¦â</p>
+<p>“Last week I wrote an article about Wicket and I spent some time discovering and taming it. And I have to confess this: I love it. … snip … Wicket is not a framework, it’s a candy bar. And everybody loves candy bars…”</p>
<p>Comment made by Romain Guy</p>
</blockquote>
<blockquote>
-<p>The issue that impressed me in the Wicket model is that âWicket does not mix markup with Java code and adds no special syntax to your markup files.â You reference Wicket identities as HTML attributes and define component properties in Java, which allows designers and programmers to work independently (within the obvious constraint of having common goals). There is no need for special tools.</p>
+<p>The issue that impressed me in the Wicket model is that “Wicket does not mix markup with Java code and adds no special syntax to your markup files.” You reference Wicket identities as HTML attributes and define component properties in Java, which allows designers and programmers to work independently (within the obvious constraint of having common goals). There is no need for special tools.</p>
-<p>From a Network World editorial entitled âNothing Sticky about Wicketâ</p>
+<p>From a Network World editorial entitled “Nothing Sticky about Wicket”</p>
</blockquote>
<blockquote>
<p>In a recent blog post I asked for feedback on what Web frameworks folks are using. Well, I got quite a surprise: Wicket was the most often recommended framework in reader emails!</p>
-<p>From an About.com article entitled And the Winner isâ¦Wicket</p>
+<p>From an About.com article entitled And the Winner is…Wicket</p>
</blockquote>
<blockquote>
-<p>âI have used Wicket since last Fall for personal projects. I have 3 kids and a wife so my free-time is very limited. Given that, I had to be very picky about which framework I chose. Iâve been very impressed with how little hassle it has been to start creating powerful, reusable components and pages with Wicket even under rather severe time constraints.â</p>
+<p>“I have used Wicket since last Fall for personal projects. I have 3 kids and a wife so my free-time is very limited. Given that, I had to be very picky about which framework I chose. I’ve been very impressed with how little hassle it has been to start creating powerful, reusable components and pages with Wicket even under rather severe time constraints.”</p>
<p>Comment on TheServerSide.com</p>
</blockquote>
<blockquote>
-<p>ââ¦after using web MVC frameworks for a couple of years, building ever more complex web applications, I moved to component based frameworks. Of these, I think Wicket is by far the bestâ¦â</p>
+<p>”…after using web MVC frameworks for a couple of years, building ever more complex web applications, I moved to component based frameworks. Of these, I think Wicket is by far the best…”</p>
<p>Comment on Manageability.org</p>
</blockquote>
<blockquote>
-<p>â⦠Talk about a mind blowing experience, it literally took me ten minutes to have a sample application up and running! The Wicket API is very Swing like, which was a welcome change for me, and allowed for a very familiar development experience. There is even an extension that allows for direct use of a Swing TreeModel. There are so many things that I like about this framework â¦â</p>
+<p>”… Talk about a mind blowing experience, it literally took me ten minutes to have a sample application up and running! The Wicket API is very Swing like, which was a welcome change for me, and allowed for a very familiar development experience. There is even an extension that allows for direct use of a Swing TreeModel. There are so many things that I like about this framework …”</p>
<p>From a blog item by the Code Poet</p>
</blockquote>
<blockquote>
-<p>âWicket has a learning flat.â</p>
+<p>“Wicket has a learning flat.”</p>
<p>Al Maw</p>
</blockquote>
@@ -257,35 +257,35 @@
<blockquote>
<p>JSF is Cool and young but Wicket is younger and even cooler. Have you tried wicket?. I am also building a large CRUD application for Job Exchange System in my country using Wicket + JPA + Stateless EJB3 + Glassfish (the latest promoted build of glassfish) and we are currently in testing phase and I am not having any serious headaches as things seems to be under control. All our forms are Ajax. We have several concurrent accesses and system is stable. I believe greatly in the Wicket Project especially for CRUD cases.</p>
-<p><a href="http://www.javalobby.org/java/forums/t90719.html#92132195">Dabar Aladejebi</a></p>
+<p><a href='http://www.javalobby.org/java/forums/t90719.html#92132195'>Dabar Aladejebi</a></p>
</blockquote>
<blockquote>
-<p>âfocuses the development efforts in the right place, inside plain Java codeâ !! This was the winning ticket for me. The framework is truly amazing. I used ever dang framework in the book and can say that Iâm most impressed with this one.</p>
+<p>“focuses the development efforts in the right place, inside plain Java code” !! This was the winning ticket for me. The framework is truly amazing. I used ever dang framework in the book and can say that I’m most impressed with this one.</p>
-<p><a href="http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html">Anonymous on JavaGeek.org</a>â <a href="http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html">Anonymous on JavaGeek.org</a></p>
+<p><a href='http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html'>Anonymous on JavaGeek.org</a>– <a href='http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html'>Anonymous on JavaGeek.org</a></p>
</blockquote>
<blockquote>
<p>Shocking simplicity. Back to the roots. Thanks.</p>
-<p><a href="http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html">joozsa on JavaGeek.org</a></p>
+<p><a href='http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html'>joozsa on JavaGeek.org</a></p>
</blockquote>
<blockquote>
<p>Wicket as far as I am concerned is the way forward for web development in Java. A lot of creativity involved though especially with the loops but It makes Web Development so much fun.</p>
-<p><a href="http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html">Anonymous on JavaGeek.org</a></p>
+<p><a href='http://javageek.org/2006/03/08/comparing_web_frameworks_wicket.html'>Anonymous on JavaGeek.org</a></p>
</blockquote>
<blockquote>
-<p>âWicket became my favorite framework in about a 24-hour period, and I think it has a very bright future. With most frameworks I see limitations, with Wicket I see possibilities. Thereâs your platitude for the day :)â</p>
+<p>“Wicket became my favorite framework in about a 24-hour period, and I think it has a very bright future. With most frameworks I see limitations, with Wicket I see possibilities. There’s your platitude for the day :)”</p>
<p>wicket-user mailing list</p>
</blockquote>
<blockquote>
-<p>âCount me in⦠Iâve only been using Wicket for maybe 2 weeks or so, and Iâm sold.â</p>
+<p>“Count me in… I’ve only been using Wicket for maybe 2 weeks or so, and I’m sold.”</p>
<p>Phillip Rhodes</p>
</blockquote>
Modified: wicket/common/site/trunk/_site/meet/features.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/features.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/features.html (original)
+++ wicket/common/site/trunk/_site/meet/features.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,87 +174,87 @@
<div id="contentbody">
<h1>Features</h1>
- <h2 id="pojo_component_model">POJO Component Model</h2>
+ <h2 id='pojo_component_model'>POJO Component Model</h2>
<p>Pages and Components in Wicket are real Java objects that support encapsulation, inheritance and events.</p>
-<h2 id="ease_of_development">Ease of Development</h2>
+<h2 id='ease_of_development'>Ease of Development</h2>
<p>Because Wicket is Java and HTML, you can leverage what you know about Java or your favorite HTML editor to write Wicket applications.</p>
-<h2 id="separation_of_concerns">Separation of Concerns</h2>
+<h2 id='separation_of_concerns'>Separation of Concerns</h2>
<p>Wicket does not mix markup with Java code and adds no special syntax to your markup files. The worlds of HTML and Java are parallel and associated only by Wicket ids, which are attributes in HTML and Component properties in Java. Since Wicket HTML is just HTML and Wicket Java is just Java, coders and designers can work independently to a large degree and without relying on any special tools.</p>
-<h2 id="secure">Secure</h2>
+<h2 id='secure'>Secure</h2>
<p>Wicket is secure by default. URLs do not expose sensitive information and all component paths are session-relative. Explicit steps must be taken to share information between sessions. Furthermore URL encryption allows highly secure web sites.</p>
-<h2 id="transparent_scalable_clustering_support">Transparent, Scalable Clustering Support</h2>
+<h2 id='transparent_scalable_clustering_support'>Transparent, Scalable Clustering Support</h2>
<p>All Wicket applications will work on a cluster automatically and without additional work. Once bottlenecks are understood, Wicket enables tuning of page state replication. The next version of Wicket will support client-side models for zero-state scalability.</p>
-<h2 id="transparent_back_button_support">Transparent Back Button Support</h2>
+<h2 id='transparent_back_button_support'>Transparent Back Button Support</h2>
<p>Wicket supports configurable page version management. When users submit a form or follow a link from a page they accessed with the back button in their browser, Wicket is able to revert the page object to the state it was in when the page was originally rendered. This means you can write web applications that support the back button with very little work.</p>
-<h2 id="multitab_and_multiwindow_support">Multi-tab and multi-window support</h2>
+<h2 id='multitab_and_multiwindow_support'>Multi-tab and multi-window support</h2>
<p>Wicket provides an easy way to write application that supports multi-window and multi-tab usage allowing developer to react properly when users open new browser window or tab</p>
-<h2 id="reusable_components">Reusable Components</h2>
+<h2 id='reusable_components'>Reusable Components</h2>
<p>Reusable components in Wicket are particularly easy to create. Not only can you extend existing components with the Java extends keyword, but you can also create Panel components which associate a group of components as a reusable unit.</p>
-<h2 id="simple_flexible_localizable_form_validation">Simple, Flexible, Localizable Form Validation</h2>
+<h2 id='simple_flexible_localizable_form_validation'>Simple, Flexible, Localizable Form Validation</h2>
<p>It is trivial to write and use validators in Wicket. It is also quite easy to customize and localize the display and content of validation error messages.</p>
-<h2 id="typesafe_sessions">Typesafe Sessions</h2>
+<h2 id='typesafe_sessions'>Typesafe Sessions</h2>
<p>Wicket eliminates the need to manage HttpSession attributes by hand. Page and component objects are transparently stored in the session and your application can create a custom session subclass with typesafe properties as well. All objects stored in the session can automatically participate in clustering replication.</p>
-<h2 id="factory_customizable">Factory Customizable</h2>
+<h2 id='factory_customizable'>Factory Customizable</h2>
<p>Wicket is very extensible. Most operations are customizable through factories or factory methods.</p>
-<h2 id="detachable_models">Detachable Models</h2>
+<h2 id='detachable_models'>Detachable Models</h2>
-<p>Model objects in Wicket can be very lightweight in terms of memory and network use in a cluster. When a model is used, it can âattachâ, populating itself with information from persistent storage. When the model is no longer in use, transient information can be reset, reducing the size of the object.</p>
+<p>Model objects in Wicket can be very lightweight in terms of memory and network use in a cluster. When a model is used, it can “attach”, populating itself with information from persistent storage. When the model is no longer in use, transient information can be reset, reducing the size of the object.</p>
-<h2 id="border_components">Border Components</h2>
+<h2 id='border_components'>Border Components</h2>
<p>Wicket Border components enable the decoration of pages in a reusable fashion. This is especially useful for inheritance of common navigational structures or layout.</p>
-<h2 id="support_for_all_basic_html_features">Support for All Basic HTML Features</h2>
+<h2 id='support_for_all_basic_html_features'>Support for All Basic HTML Features</h2>
-<p>Wicket supports image tags, links, forms and everything else that youâre used to using in your web application development.</p>
+<p>Wicket supports image tags, links, forms and everything else that you’re used to using in your web application development.</p>
-<h2 id="programmatic_manipulation_of_attributes">Programmatic Manipulation of Attributes</h2>
+<h2 id='programmatic_manipulation_of_attributes'>Programmatic Manipulation of Attributes</h2>
<p>Wicket Components can programmatically change any HTML tag attribute.</p>
-<h2 id="automatic_conversions">Automatic Conversions</h2>
+<h2 id='automatic_conversions'>Automatic Conversions</h2>
<p>Once a Form validates, the model can be updated using Wicket converters. Most ordinary conversions are built-in and it is easy to write new converters.</p>
-<h2 id="dynamic_images">Dynamic Images</h2>
+<h2 id='dynamic_images'>Dynamic Images</h2>
<p>Wicket makes image use, sharing and generation very easy. Dynamic images can be created by simply implementing a paint method.</p>
-<h2 id="pageable_listview">Pageable ListView</h2>
+<h2 id='pageable_listview'>Pageable ListView</h2>
<p>ListViews in Wicket are extremely powerful. You can nest any kind of component in a ListView row, even other ListViews. PageableListView supports navigation links for large lists.</p>
-<h2 id="tree_component">Tree Component</h2>
+<h2 id='tree_component'>Tree Component</h2>
<p>Out of the box tree component for navigating and selecting nodes.</p>
-<h2 id="localization">Localization</h2>
+<h2 id='localization'>Localization</h2>
<p>HTML pages, images and resource strings can all be localized.</p>
-<h2 id="examples">Examples</h2>
+<h2 id='examples'>Examples</h2>
<p>Wicket has numerous examples showcasing all of the above features.</p>
</div>
Modified: wicket/common/site/trunk/_site/meet/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/index.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/index.html (original)
+++ wicket/common/site/trunk/_site/meet/index.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
Modified: wicket/common/site/trunk/_site/meet/introduction.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/introduction.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/introduction.html (original)
+++ wicket/common/site/trunk/_site/meet/introduction.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -176,11 +176,11 @@
<h1>Meet Apache Wicket</h1>
<p>By Jonathan Locke, original author of Wicket</p>
-<h2 id="why_wicket">Why Wicket?</h2>
+<h2 id='why_wicket'>Why Wicket?</h2>
<p>If you are looking to do web application programming in Java, you have a very large number of choices these days. In fact, there are so many web application frameworks now that it has become somewhat of a joke. One blog site on the Internet poses the question: How many Java web frameworks can you name? The answer they show looks like this:</p>
-<h2 id="frameworks_frameworks_everywhere">Frameworks, Frameworks Everywhere</h2>
+<h2 id='frameworks_frameworks_everywhere'>Frameworks, Frameworks Everywhere</h2>
<TABLE class='confluenceTable'><TBODY>
<TR>
<TD class='confluenceTd'>Echo</TD>
@@ -273,25 +273,25 @@
<TD class='confluenceTd'> </TD>
</TR>
</TBODY></TABLE>
-<h2 id="why_reinvent_the_wheel">Why âReinvent the Wheelâ?</h2>
+<h2 id='why_reinvent_the_wheel'>Why “Reinvent the Wheel”?</h2>
-<p>In light of this, you may be wondering âWhat good is another web application framework?â Indeed. Why âre-invent the wheel?â One snappy comeback to that old saw is: because this time we could make it rounder!</p>
+<p>In light of this, you may be wondering “What good is another web application framework?” Indeed. Why “re-invent the wheel?” One snappy comeback to that old saw is: because this time we could make it rounder!</p>
<p>But it was not simply a desire for higher quality that drove the creation of Wicket. Even with so many options, there really is no web toolkit which fills exactly the niche that Wicket fills. In fact, Wicket is quite unlike each of the frameworks above.</p>
-<p>Wicketâs closest cousins are probably Tapestry and Echo, but even there the likeness is very shallow. Like Tapestry, Wicket uses a special HTML attribute to denote components, enabling easy editing with ordinary HTML editors. Like Echo, Wicket has a first-class component model. But Wicket applications are not like applications written in either Tapestry or Echo, because in Wicket you get the best of both worlds. You get the benefits of a first-class component model and a non-intrusive approach to HTML. In many situations, this combination may prove to be a significant development advantage.</p>
+<p>Wicket’s closest cousins are probably Tapestry and Echo, but even there the likeness is very shallow. Like Tapestry, Wicket uses a special HTML attribute to denote components, enabling easy editing with ordinary HTML editors. Like Echo, Wicket has a first-class component model. But Wicket applications are not like applications written in either Tapestry or Echo, because in Wicket you get the best of both worlds. You get the benefits of a first-class component model and a non-intrusive approach to HTML. In many situations, this combination may prove to be a significant development advantage.</p>
<p>To understand why Wicket is so different, it may help to understand the motivations that created it.</p>
-<h2 id="motivations">Motivations</h2>
+<h2 id='motivations'>Motivations</h2>
-<h3 id="most_existing_web_frameworks_provide_weak_to_nonexistent_support_in_managing_serverside_state">Most existing web frameworks provide weak to non-existent support in managing server-side state</h3>
+<h3 id='most_existing_web_frameworks_provide_weak_to_nonexistent_support_in_managing_serverside_state'>Most existing web frameworks provide weak to non-existent support in managing server-side state</h3>
<p>This normally means lots of ad-hoc code in web applications dealing with the gory mechanics of state management. While Wicket will not allow you to stop thinking about server state, it goes a long ways towards making it easy and often transparent to manage that state.</p>
-<p>In Wicket, all server side state is automatically managed. You will never directly use an HttpSession object or similar wrapper to store state. Instead, state is associated with components. Each server-side page component holds a nested hierarchy of stateful components, where each componentâs model is, in the end, a POJO (Plain Old Java Object). Wicket maintains a map of these pages in each userâs session. One purpose of this page map (and the component hierarchy on each page) is to allow the framework to hide all details of how your components and models are accessed. You deal with simple, familiar Java objects and Wicket deals with things like URLs, session ids and GET/POST requests.</p>
+<p>In Wicket, all server side state is automatically managed. You will never directly use an HttpSession object or similar wrapper to store state. Instead, state is associated with components. Each server-side page component holds a nested hierarchy of stateful components, where each component’s model is, in the end, a POJO (Plain Old Java Object). Wicket maintains a map of these pages in each user’s session. One purpose of this page map (and the component hierarchy on each page) is to allow the framework to hide all details of how your components and models are accessed. You deal with simple, familiar Java objects and Wicket deals with things like URLs, session ids and GET/POST requests.</p>
-<p>You will also find that this well-structured server state makes it very easy to deal with the dreaded âback button problemâ. In fact, Wicket has a generic and robust solution which can identify and expire browser-cached pages that have become stale due to structural changes to the model of a component on the page.</p>
+<p>You will also find that this well-structured server state makes it very easy to deal with the dreaded “back button problem”. In fact, Wicket has a generic and robust solution which can identify and expire browser-cached pages that have become stale due to structural changes to the model of a component on the page.</p>
<p>Finally, Wicket has been designed to work with POJO persistence frameworks such as JDO or Hibernate. This can make database driven web applications quite easy to write.</p>
@@ -299,33 +299,33 @@
<p>In terms of efficiency versus productivity, perhaps Wicket is to JSP as Java is to C. You can accomplish anything in Wicket in JSP. You may even do it more efficiently in terms of memory or processor consumption. But it may take you weeks or months longer to develop your application. And in the end, since state management in JSP is ad-hoc, you are likely find security problems and bugs popping up everywhere. Most of the other frameworks above will do only a little more to help you.</p>
-<h3 id="most_existing_frameworks_require_special_html_code">Most existing frameworks require special HTML code</h3>
+<h3 id='most_existing_frameworks_require_special_html_code'>Most existing frameworks require special HTML code</h3>
<p>JSP is by far the worst offender, allowing the embedding of Java code directly in web pages, but to some degree almost all of the frameworks from the list (except Tapestry) above introduce some kind of special syntax to your HTML code.</p>
<p>Special syntax is highly undesirable because it changes the nature of HTML from the kind of pure-and-simple HTML markup that web designers are familiar with, to some kind of special HTML. This special HTML can be more difficult to preview, edit and understand.</p>
-<p>Wicket does not introduce any special syntax to HTML. Instead, it extends HTML in a standards-compliant way via a Wicket namespace that is fully compliant with the XHTML standard. This means that you can use Macromedia Dreamweaver, Microsoft Front Page, Word, Adobe Go Live, or any other existing HTML editor to work on your web pages and Wicket components. To accomplish this, Wicket consistently uses a single id attribute in the Wicket namespace (âwicket:idâ) to mark HTML tags that should receive special treatment by the toolkit. If you prefer not to render Wicket namespaced tags and attributes to your end-users, Wicket has a simple setting to strip them all out, resulting in ordinary, standards-compliant HTML.</p>
+<p>Wicket does not introduce any special syntax to HTML. Instead, it extends HTML in a standards-compliant way via a Wicket namespace that is fully compliant with the XHTML standard. This means that you can use Macromedia Dreamweaver, Microsoft Front Page, Word, Adobe Go Live, or any other existing HTML editor to work on your web pages and Wicket components. To accomplish this, Wicket consistently uses a single id attribute in the Wicket namespace (“wicket:id”) to mark HTML tags that should receive special treatment by the toolkit. If you prefer not to render Wicket namespaced tags and attributes to your end-users, Wicket has a simple setting to strip them all out, resulting in ordinary, standards-compliant HTML.</p>
-<p>No âspecial sauceâ in your HTML means designers can mock up pages that you can use directly in development. Adding Java components to the HTML is as simple as setting the component name attribute. And you can then give the HTML back to your web designers knowing that they can change it with confidence.</p>
+<p>No “special sauce” in your HTML means designers can mock up pages that you can use directly in development. Adding Java components to the HTML is as simple as setting the component name attribute. And you can then give the HTML back to your web designers knowing that they can change it with confidence.</p>
-<p>Wicket, more than any other framework gives you a separation of concerns. Web designers can work on the HTML with very little knowledge of the application code (they cannot remove the component name tags and they cannot arbitrarily change the nesting of components, but anything else goes). Likewise, coders can work on the Java components that attach to the HTML without concerning themselves with what a given page looks like. By not stepping on each otherâs toes, everyone can get more work done.</p>
+<p>Wicket, more than any other framework gives you a separation of concerns. Web designers can work on the HTML with very little knowledge of the application code (they cannot remove the component name tags and they cannot arbitrarily change the nesting of components, but anything else goes). Likewise, coders can work on the Java components that attach to the HTML without concerning themselves with what a given page looks like. By not stepping on each other’s toes, everyone can get more work done.</p>
-<h3 id="existing_frameworks_are_not_easy">Existing frameworks are not easy</h3>
+<h3 id='existing_frameworks_are_not_easy'>Existing frameworks are not easy</h3>
<p>Most of the existing toolkits have poorly defined or non-existent object models. In some cases, the model is defined using special XML syntaxes. The syntaxes may be so cumbersome that special tools are required to manipulate all the configuration information. Since these toolkits are not simple Java libraries you may or may not be able to use your favorite IDE tools such as editors, debuggers and compilers.</p>
<p>Wicket is all about simplicity. There are no configuration files to learn in Wicket. Wicket is a simple class library with a consistent approach to component structure. In Wicket, your web applications will more closely resemble a Swing application than a JSP application. If you know Java (and especially if you know Swing), you already know a lot about Wicket.</p>
-<h3 id="existing_frameworks_inhibit_reusability">Existing frameworks inhibit reusability</h3>
+<h3 id='existing_frameworks_inhibit_reusability'>Existing frameworks inhibit reusability</h3>
-<p>Tapestry and JSF at least have component models that allow reuse, but you are likely to find that it is not particularly trivial to do, at least when compared with Wicket. Wicket has been explicitly designed to make it very, very easy to create reusable components. Itâs surprisingly simple to extend existing components and to make compound components such as a SignInPanel or AddressForm. It is also relatively easy to create components that exploit new features of browsers. Components in Wicket can be packaged up in JAR files and reused by simply dropping them in your lib folder - no configuration necessary!</p>
+<p>Tapestry and JSF at least have component models that allow reuse, but you are likely to find that it is not particularly trivial to do, at least when compared with Wicket. Wicket has been explicitly designed to make it very, very easy to create reusable components. It’s surprisingly simple to extend existing components and to make compound components such as a SignInPanel or AddressForm. It is also relatively easy to create components that exploit new features of browsers. Components in Wicket can be packaged up in JAR files and reused by simply dropping them in your lib folder - no configuration necessary!</p>
-<h3 id="web_programming_should_be_fun">Web programming should be fun!</h3>
+<h3 id='web_programming_should_be_fun'>Web programming should be fun!</h3>
<p>This is my most personal goal for writing Wicket . None of the existing frameworks are appealing to me in terms of intuitiveness, quickness, ease of development, etc. It is my hope that Wicket represents a significant step in the direction of making web applications easy and fun to write.</p>
-<h2 id="goals">Goals</h2>
+<h2 id='goals'>Goals</h2>
<p>Coming from these motivations, the following goals for Wicket emerged:</p>
@@ -338,7 +338,7 @@
<li>All code written in Java ala Swing</li>
-<li>Minimize âconceptual surface areaâ</li>
+<li>Minimize “conceptual surface area”</li>
<li>Avoid overuse of XML configuration files</li>
@@ -412,7 +412,7 @@
<p>COMPLETE</p>
<ul>
-<li>The Wicket team is committed to deliver a feature complete, ready-to-use framework for developing Java web applications. The core framework was written and contributed by the author of this introduction, Jonathan Locke. The current team consists of a group of experienced programmers, some of which were active on some of the other frameworks stated above, and all of which have extensive experience building large scale Java web applications. We eat our own dogfood, and will thus work on Wicket from a framework userâs perspective.</li>
+<li>The Wicket team is committed to deliver a feature complete, ready-to-use framework for developing Java web applications. The core framework was written and contributed by the author of this introduction, Jonathan Locke. The current team consists of a group of experienced programmers, some of which were active on some of the other frameworks stated above, and all of which have extensive experience building large scale Java web applications. We eat our own dogfood, and will thus work on Wicket from a framework user’s perspective.</li>
</ul>
</li>
</ul>
Modified: wicket/common/site/trunk/_site/meet/vision.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/meet/vision.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/vision.html (original)
+++ wicket/common/site/trunk/_site/meet/vision.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -184,7 +184,7 @@
<p>I once heard Josh Bloch talk about the power to weight ratio of an API. The highest compliment anyone could make of Wicket would be to suggest that Wicket has a lot of power and not much conceptual surface area.</p>
-<p>In art, negative space is the part thatâs not the subject. In music, negative space is the rest. In software, negative space is all the code that you managed to avoid writing. In all three disciplines, itâs what separates what is truly excellent from what is merely good.</p>
+<p>In art, negative space is the part that’s not the subject. In music, negative space is the rest. In software, negative space is all the code that you managed to avoid writing. In all three disciplines, it’s what separates what is truly excellent from what is merely good.</p>
<p>Following this metaphor, if Wicket is our foreground object, it is defined in a negative sense by all the things that it is not (by the background).</p>
@@ -192,13 +192,13 @@
<p>The more ways that Wicket can find to offload responsibilities (both now and in the future), the less it will be. And thus, the more it will be.</p>
-<p>The difficulty moving forward with Wicket will be balancing all the day-to-day needs people are going to be bringing up with this overall vision of minimalism. There ultimately will be compromises, and the âtrickâ to making the right compromises is simply to agonize over all the options for a long time and then to only make the compromises that everyone agrees are really essential to what Wicket needs to be and do.</p>
+<p>The difficulty moving forward with Wicket will be balancing all the day-to-day needs people are going to be bringing up with this overall vision of minimalism. There ultimately will be compromises, and the “trick” to making the right compromises is simply to agonize over all the options for a long time and then to only make the compromises that everyone agrees are really essential to what Wicket needs to be and do.</p>
-<p>A big part of this process of agonizing is to act like doctors and âfirst, do no harmâ. If some issue isnât sitting well with everyone yet, thereâs probably a reason for that. So, maybe the near-term solution is to simply do nothing and let people use the existing functionality until the limits to that approach (as well as competing ideas) are better understood.</p>
+<p>A big part of this process of agonizing is to act like doctors and “first, do no harm”. If some issue isn’t sitting well with everyone yet, there’s probably a reason for that. So, maybe the near-term solution is to simply do nothing and let people use the existing functionality until the limits to that approach (as well as competing ideas) are better understood.</p>
-<p>Itâs easy to add features. Itâs often impossible to change or remove them.</p>
+<p>It’s easy to add features. It’s often impossible to change or remove them.</p>
-<p>Given this, the Wicket approach to the overall problem of evolving while keeping a high power to weight ratio will be partitioning off all controversial new ideas in a âwicket-stuffâ package until they are broadly accepted. This way people can experiment and code away and check in lots of stuff without affecting the main codebase with untested ideas. Then, when ideas pan out to everyoneâs satisfaction, the leads of the project will move them into the core.</p>
+<p>Given this, the Wicket approach to the overall problem of evolving while keeping a high power to weight ratio will be partitioning off all controversial new ideas in a “wicket-stuff” package until they are broadly accepted. This way people can experiment and code away and check in lots of stuff without affecting the main codebase with untested ideas. Then, when ideas pan out to everyone’s satisfaction, the leads of the project will move them into the core.</p>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/start/download.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/start/download.html?rev=1590290&r1=1590289&r2=1590290&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/start/download.html (original)
+++ wicket/common/site/trunk/_site/start/download.html Sat Apr 26 20:03:27 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.15.0">Wicket 6.15</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">Wicket 1.5</a>
@@ -174,29 +174,29 @@
<div id="contentbody">
<h1>Download Wicket releases</h1>
- <p>Apache Wicket 6.14.0 is the current stable release. Most users get Apache Wicket using <a href="#maven">Apache Mavenâs dependency management</a>, which incidentally is the most convenient way of obtaining the latest and greatest Wicket.</p>
+ <p>Apache Wicket 6.15.0 is the current stable release. Most users get Apache Wicket using <a href='#maven'>Apache Maven’s dependency management</a>, which incidentally is the most convenient way of obtaining the latest and greatest Wicket.</p>
-<h2 id="download">Download</h2>
+<h2 id='download'>Download</h2>
-<p>New projects should use <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">Wicket 6.14.0</a> as their base.</p>
+<p>New projects should use <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.15.0'>Wicket 6.15.0</a> as their base.</p>
<ul>
-<li><strong>Latest stable release</strong>: <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">6.14.0</a></li>
+<li><strong>Latest stable release</strong>: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.15.0'>6.15.0</a></li>
-<li><strong>Latest 6.x release</strong>: <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.14.0">6.14.0</a></li>
+<li><strong>Latest 6.x release</strong>: <a href='http://www.apache.org/dyn/closer.cgi/wicket/6.15.0'>6.15.0</a></li>
-<li><strong>Latest 1.5.x release</strong>: <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.11">1.5.11</a></li>
+<li><strong>Latest 1.5.x release</strong>: <a href='http://www.apache.org/dyn/closer.cgi/wicket/1.5.11'>1.5.11</a></li>
-<li><strong>Latest 1.4.x release</strong> (security updates only): <a href="http://www.apache.org/dyn/closer.cgi/wicket/1.4.23">1.4.23</a></li>
+<li><strong>Latest 1.4.x release</strong> (security updates only): <a href='http://www.apache.org/dyn/closer.cgi/wicket/1.4.23'>1.4.23</a></li>
-<li><strong>Archived releases</strong>: <a href="http://archive.apache.org/dist/wicket">http://archive.apache.org/dist/wicket</a></li>
+<li><strong>Archived releases</strong>: <a href='http://archive.apache.org/dist/wicket'>http://archive.apache.org/dist/wicket</a></li>
</ul>
-<p>We recommend you <a href="quickstart.html">start</a> with our latest stable release.</p>
+<p>We recommend you <a href='quickstart.html'>start</a> with our latest stable release.</p>
-<h3 id="requirements">Requirements</h3>
+<h3 id='requirements'>Requirements</h3>
-<h4 id="java_version">Java version</h4>
+<h4 id='java_version'>Java version</h4>
<ul>
<li>Apache Wicket 6.x requires JDK 6.0 or newer</li>
@@ -206,39 +206,39 @@
<li>Apache Wicket 1.4.x requires JDK 1.5 or newer</li>
</ul>
-<h4 id="mixing_wicket_versions">Mixing Wicket versions</h4>
+<h4 id='mixing_wicket_versions'>Mixing Wicket versions</h4>
<p>You cannot mix different Wicket versions in your project. You should always use the artifacts from a particular release train.</p>
<p>For example it is <strong>NOT</strong> possible to use Wicket Extensions 1.5 in a Wicket 6 project. The same goes for 3rd party libraries: make sure you always use a compatible version of your 3rd party library.</p>
-<h4 id="logging">Logging</h4>
+<h4 id='logging'>Logging</h4>
-<p>You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use <a href="http://logging.apache.org/log4j">log4j</a>.</p>
+<p>You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use <a href='http://logging.apache.org/log4j'>log4j</a>.</p>
-<p>If you do, just include <strong>slf4j-log4j12.jar</strong> on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the <a href="http://www.slf4j.org/faq.html">SLF4J site</a> for more information.</p>
+<p>If you do, just include <strong>slf4j-log4j12.jar</strong> on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the <a href='http://www.slf4j.org/faq.html'>SLF4J site</a> for more information.</p>
-<h2 id="migrating_from_earlier_versions">Migrating from earlier versions</h2>
+<h2 id='migrating_from_earlier_versions'>Migrating from earlier versions</h2>
<p>If you are migrating an existing application from earlier versions of Wicket you may find our migration guides invaluable:</p>
<ul>
-<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.3">Wicket 1.2 to Wicket 1.3</a></li>
+<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.3'>Wicket 1.2 to Wicket 1.3</a></li>
-<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.4">Wicket 1.3 to Wicket 1.4</a></li>
+<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migrating+to+Wicket+1.4'>Wicket 1.3 to Wicket 1.4</a></li>
-<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5">Wicket 1.4 to Wicket 1.5</a></li>
+<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+1.5'>Wicket 1.4 to Wicket 1.5</a></li>
-<li>Migrating from <a href="https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0">Wicket 1.5 to Wicket 6</a></li>
+<li>Migrating from <a href='https://cwiki.apache.org/confluence/display/WICKET/Migration+to+Wicket+6.0'>Wicket 1.5 to Wicket 6</a></li>
</ul>
-<h2 id="maven">Maven</h2>
+<h2 id='maven'>Maven</h2>
<p>Add the following snippet to your Maven project descriptor (<code>pom.xml</code>):</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><dependency></span>
<span class='nt'><groupId></span>org.apache.wicket<span class='nt'></groupId></span>
<span class='nt'><artifactId></span>wicket-core<span class='nt'></artifactId></span>
- <span class='nt'><version></span>6.14.0<span class='nt'></version></span>
+ <span class='nt'><version></span>6.15.0<span class='nt'></version></span>
<span class='nt'></dependency></span>
</code></pre></div>
<p>For the SLF4J log4j binding:</p>
@@ -248,7 +248,7 @@
<span class='nt'><version></span>1.6.4<span class='nt'></version></span>
<span class='nt'></dependency></span>
</code></pre></div>
-<h2 id="snapshots_and_latest_bleedingedge_code">SNAPSHOTs and latest bleeding-edge code</h2>
+<h2 id='snapshots_and_latest_bleedingedge_code'>SNAPSHOTs and latest bleeding-edge code</h2>
<p>If you wish to build the latest code from scratch, master and branches live in the Git repository: https://git-wip-us.apache.org/repos/asf/wicket.git</p>
@@ -268,7 +268,7 @@
<li><strong>1.2.x</strong>: wicket-1.2.x</li>
</ul>
-<p>Thereâs also a Maven 2 repository providing SNAPSHOTs available here:</p>
+<p>There’s also a Maven 2 repository providing SNAPSHOTs available here:</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><repositories></span>
<span class='nt'><repository></span>
<span class='nt'><releases></span>