You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by da...@apache.org on 2014/01/13 17:02:26 UTC
svn commit: r1557758 [10/11] - in /wicket/common/site/trunk: ./ _includes/
_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/ ...
Modified: wicket/common/site/trunk/_site/learn/examples/dropdownchoice.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/dropdownchoice.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/dropdownchoice.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/dropdownchoice.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -174,11 +174,11 @@
<div id="contentbody">
<h1>Using the DropDownChoice component</h1>
- <p>One of the most problematic components for beginners of Wicket is the <code>DropDownChoice</code> component. In this example we will work the component to give a little more insight into its workings. This example requires that you have some understanding of the Wicket component model (nothing fancy though, but you might want to read the other examples first), and the Model concept used in Wicket (you can read more on models <a href='https://cwiki.apache.org/confluence/display/WICKET/Working+with+Wicket+models'>here</a>).</p>
+ <p>One of the most problematic components for beginners of Wicket is the <code>DropDownChoice</code> component. In this example we will work the component to give a little more insight into its workings. This example requires that you have some understanding of the Wicket component model (nothing fancy though, but you might want to read the other examples first), and the Model concept used in Wicket (you can read more on models <a href="https://cwiki.apache.org/confluence/display/WICKET/Working+with+Wicket+models">here</a>).</p>
-<h2 id='the_example_domain'>The example domain</h2>
+<h2 id="the_example_domain">The example domain</h2>
-<p>The <code>DropDownChoice</code> component is typically used <em>inside</em> a form. This example will expand on that usage. The component is particularly designed to work with objects. So let’s say we have a list of people and we want to select the manager of an employee.</p>
+<p>The <code>DropDownChoice</code> component is typically used <em>inside</em> a form. This example will expand on that usage. The component is particularly designed to work with objects. So letâs say we have a list of people and we want to select the manager of an employee.</p>
<div class='highlight'><pre><code class='java'><span class='kd'>public</span> <span class='kd'>class</span> <span class='nc'>Person</span> <span class='o'>{</span>
<span class='kd'>private</span> <span class='n'>Long</span> <span class='n'>id</span><span class='o'>;</span>
<span class='kd'>private</span> <span class='n'>String</span> <span class='n'>name</span><span class='o'>;</span>
@@ -201,7 +201,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h2 id='the_assign_manager_page'>The assign manager page</h2>
+<h2 id="the_assign_manager_page">The assign manager page</h2>
<p>Next we want to create a page where we assign a manager to an employee. This is how the page would look like in HTML:</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
@@ -239,7 +239,7 @@
<p>We will focus on the select box, because that will be our <code>DropDownChoice</code>. The <code><option></code> tags are there for preview, our component will replace them with the generated choices.</p>
-<p>Let’s see how the page looks like from the Java side:</p>
+<p>Letâs see how the page looks like from the Java side:</p>
<div class='highlight'><pre><code class='java'><span class='kd'>public</span> <span class='kd'>class</span> <span class='nc'>AssignManagerPage</span> <span class='kd'>extends</span> <span class='n'>WebPage</span> <span class='o'>{</span>
<span class='kd'>public</span> <span class='nf'>AssignManagerPage</span><span class='o'>(</span><span class='n'>Person</span> <span class='n'>employee</span><span class='o'>)</span> <span class='o'>{</span>
<span class='n'>Form</span> <span class='n'>form</span> <span class='o'>=</span> <span class='k'>new</span> <span class='n'>Form</span><span class='o'>(</span><span class='s'>"form"</span><span class='o'>);</span>
@@ -280,7 +280,7 @@
</code></pre></div>
<p>As you can see from this markup is that Wicket added the items of the managers list and numbered the values of the options. These are the indices of the items in the list. If the order of the list can change between requests, <em>or</em> if the list itself can change, then please use an <code>IChoiceRenderer</code>.</p>
-<h2 id='selecting_a_choice'>Selecting a choice</h2>
+<h2 id="selecting_a_choice">Selecting a choice</h2>
<p>Now if a user selects a value and submits the form, Wicket will assign the manager to the employee (the <code>PropertyModel</code> takes care of that). The following list shows what basically happens:</p>
@@ -291,14 +291,14 @@
<li>render page, selected value is <code>"Choose one"</code></li>
-<li>user selects “Eric Cartman” and submits form</li>
+<li>user selects âEric Cartmanâ and submits form</li>
-<li>Wicket assigns manager “Eric Cartman” to <code>managedBy</code> field of the employee</li>
+<li>Wicket assigns manager âEric Cartmanâ to <code>managedBy</code> field of the employee</li>
</ol>
<p>So there is no need for getting or setting the value from the drop down component: Wicket binds directly to your domain objects if you use the correct models.</p>
-<h2 id='selecting_a_default_choice'>Selecting a default choice</h2>
+<h2 id="selecting_a_default_choice">Selecting a default choice</h2>
<p>If you want to select a default value for the manager, then all you need to do is assign the default manager to the employee and Wicket will take care of the rest:</p>
<div class='highlight'><pre><code class='java'><span class='c1'>// some add new employee code</span>
@@ -308,7 +308,7 @@
<span class='n'>setResponsePage</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>AssignManagerPage</span><span class='o'>(</span><span class='n'>newEmployee</span><span class='o'>));</span>
</code></pre></div>
-<h2 id='summary'>Summary</h2>
+<h2 id="summary">Summary</h2>
<p>This concludes the (small) example of using a <code>DropDownChoice</code> component correctly. The ideas behind Wicket are perfectly reflected in this component: work with your domain objects, bind them to your components and get on with the rest of your application.</p>
</div>
Modified: wicket/common/site/trunk/_site/learn/examples/guestbook.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/guestbook.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/guestbook.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/guestbook.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -176,11 +176,11 @@
<h1>Guestbook</h1>
<p>The GuestBook application allows users to enter comments that appear on a page like a weblog. Drawing the list of comments is very easy with the Wicket <code>ListView</code> component. This example also gives an impression of what form handling is like.</p>
-<p><img src='guestbook.png' alt='Guestbook screenshot' /></p>
+<p><img src="guestbook.png" alt="Guestbook screenshot" /></p>
<p>As with all examples, you have to put all files in the same package directory. This means putting the markup files and the java files next to one another. It is possible to alter this behavior, but that is beyond the scope of this example.</p>
-<h2 id='commentjava'>Comment.java</h2>
+<h2 id="commentjava">Comment.java</h2>
<p>The Comment POJO model is very straightforward:</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>org</span><span class='o'>.</span><span class='na'>apache</span><span class='o'>.</span><span class='na'>wicket</span><span class='o'>.</span><span class='na'>examples</span><span class='o'>.</span><span class='na'>guestbook</span><span class='o'>;</span>
@@ -221,7 +221,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h2 id='guestbookjava'>GuestBook.java</h2>
+<h2 id="guestbookjava">GuestBook.java</h2>
<p>In the file <code>GuestBook.java</code> we have put the Java component code for the guestbook page. This is the homepage for the guestbook application. The page consists of a form for entering new items to the guestbook and a list of repeating markup for showing the guestbook entries.</p>
@@ -326,9 +326,9 @@
<p>We use a synchronized list as our shared static model used by <code>commentListView</code> (<code>commentList</code>) to ensure that it is only updated by one thread at a time. Remember, this is a multi-user application with a shared model!</p>
-<p>Finally, you may notice the call to <code>commentListView.modelChanged()</code>. This informs the list view that its model has been modified. In more advanced usage scenarios, this would allow Wicket to expire stale pages accessed with the browser’s back button.</p>
+<p>Finally, you may notice the call to <code>commentListView.modelChanged()</code>. This informs the list view that its model has been modified. In more advanced usage scenarios, this would allow Wicket to expire stale pages accessed with the browserâs back button.</p>
-<h2 id='guestbookhtml'>GuestBook.html</h2>
+<h2 id="guestbookhtml">GuestBook.html</h2>
<p>In the HTML below, notice the way that the <code>TextArea</code> component is being nested inside the <code>CommentForm</code>. Wicket is able to keep everything straight because the Java <code>Component.add()</code> calls have to result in the same nesting structure as the HTML.</p>
@@ -365,9 +365,9 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<h2 id='guestbookapplicationjava'>GuestBookApplication.java</h2>
+<h2 id="guestbookapplicationjava">GuestBookApplication.java</h2>
-<p>For completeness, we’ve included the <code>GuestBookApplication</code> class, and as a final treat the modifications to the <code>web.xml</code> file.</p>
+<p>For completeness, weâve included the <code>GuestBookApplication</code> class, and as a final treat the modifications to the <code>web.xml</code> file.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>org</span><span class='o'>.</span><span class='na'>apache</span><span class='o'>.</span><span class='na'>wicket</span><span class='o'>.</span><span class='na'>examples</span><span class='o'>.</span><span class='na'>guestbook</span><span class='o'>;</span>
<span class='kn'>import</span> <span class='nn'>org.apache.wicket.Page</span><span class='o'>;</span>
@@ -383,7 +383,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h2 id='webxml'>web.xml</h2>
+<h2 id="webxml">web.xml</h2>
<p>Add the following two sections (servlet and servlet-mapping) to your web.xml file for running this application.</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><filter></span>
Modified: wicket/common/site/trunk/_site/learn/examples/helloworld.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/helloworld.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/helloworld.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/helloworld.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -180,7 +180,7 @@
<p>If you wish to start building this example, you may want to take a look at the Wicket Quickstart project, which provides a quick way of getting up and running without having to figure things out yourself. The Quickstart project contains the necessary build files (Ant and Maven), libraries, minimal set of Java and markup files and an embedded Jetty server to run your application without having to go through the whole build-deploy cycle.</p>
-<h3 id='helloworldapplicationjava'>HelloWorldApplication.java</h3>
+<h3 id="helloworldapplicationjava">HelloWorldApplication.java</h3>
<p>Each Wicket application is defined by an Application object. This object defines what the home page is, and allows for some configuration.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>import</span> <span class='nn'>org.apache.wicket.protocol.http.WebApplication</span><span class='o'>;</span>
@@ -200,7 +200,7 @@
</code></pre></div>
<p>Here you can see that we define <code>wicket.examples.helloworld.HelloWorld</code> to be our home page. When the base URL of our application is requested, the markup rendered by the HelloWorld page is returned.</p>
-<h3 id='helloworldjava'>HelloWorld.java</h3>
+<h3 id="helloworldjava">HelloWorld.java</h3>
<div class='highlight'><pre><code class='java'><span class='kn'>import</span> <span class='nn'>org.apache.wicket.markup.html.WebPage</span><span class='o'>;</span>
<span class='kn'>import</span> <span class='nn'>org.apache.wicket.markup.html.basic.Label</span><span class='o'>;</span>
@@ -214,17 +214,17 @@
<ol>
<li>
-<p>“message”</p>
+<p>âmessageâ</p>
</li>
<li>
-<p>“Hello World!”</p>
+<p>âHello World!â</p>
</li>
</ol>
<p>The first parameter is the component identifier, which Wicket uses to identify the <code>Label</code> component in your HTML markup. The second parameter is the message which the <code>Label</code> should render.</p>
-<h3 id='helloworldhtml'>HelloWorld.html</h3>
+<h3 id="helloworldhtml">HelloWorld.html</h3>
<p>The HTML file that defines our Hello World functionality is as follows:</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
@@ -247,7 +247,7 @@
<p>The component declaration consists of the Wicket identifier <code>wicket:id</code> and the component identifier <code>message</code>. The component identifier should be the same as the name of the component you defined in your <code>WebPage</code>. The text between the <code><span></code> tags is removed when the component renders its message. The final content of the component is determined by your Java code.</p>
-<h3 id='webxml'>web.xml</h3>
+<h3 id="webxml">web.xml</h3>
<p>In order to deploy our HelloWorld program, we need to make our application known to the application server by means of the web.xml file.</p>
<div class='highlight'><pre><code class='xml'><span class='cp'><?xml version="1.0" encoding="UTF-8"?></span>
@@ -275,9 +275,9 @@
<p>Also, notice the url-mapping to /*. The Wicket filter will only process requests that are Wicket requests. If a request is not Wicket related, the filter will pass the request on to the chain. This ensures that (static) resources outside the realm of the Wicket application, such as style sheets, JavaScript files, images and so forth will be served by the container.</p>
-<h2 id='ready_to_deploy'>Ready to deploy</h2>
+<h2 id="ready_to_deploy">Ready to deploy</h2>
-<p>That’s it. No more configuration necessary! All you need to do now is to deploy the web application into your favorite application server. Point your browser to the url: <code>http://<servername>/<warfilename>/</code>, substituting servername and warfilename to the appropriate values, such as http://localhost:8080/helloworld/.</p>
+<p>Thatâs it. No more configuration necessary! All you need to do now is to deploy the web application into your favorite application server. Point your browser to the url: <code>http://<servername>/<warfilename>/</code>, substituting servername and warfilename to the appropriate values, such as http://localhost:8080/helloworld/.</p>
<p>As you can see: no superfluous XML configuration files are needed to enable a Wicket application. Only the markup (HTML) files, the Java class files and the required web.xml were needed to create this application.</p>
</div>
Modified: wicket/common/site/trunk/_site/learn/examples/index.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/index.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/index.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/index.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -174,24 +174,24 @@
<div id="contentbody">
<h1>A Quick Tour of Wicket</h1>
- <p>Nothing says more about a development technology than a few simple examples. After all, how hard should it be to do something easy? The examples below should speak for themselves in demonstrating how easy it is to get things done in Wicket when compared to other frameworks. You will discover that Wicket’s component-oriented structure and its “low touch” approach to HTML is quite inviting.</p>
+ <p>Nothing says more about a development technology than a few simple examples. After all, how hard should it be to do something easy? The examples below should speak for themselves in demonstrating how easy it is to get things done in Wicket when compared to other frameworks. You will discover that Wicketâs component-oriented structure and its âlow touchâ approach to HTML is quite inviting.</p>
-<p>You can see these examples and many more in <a href='http://www.wicket-library.com/wicket-examples-6.0.x'>live action</a> without having to install anything.</p>
+<p>You can see these examples and many more in <a href="http://www.wicket-library.com/wicket-examples-6.0.x">live action</a> without having to install anything.</p>
<ul>
-<li><a href='helloworld.html'>Hello World!</a> - Everybody’s favorite example</li>
+<li><a href="helloworld.html">Hello World!</a> - Everybodyâs favorite example</li>
-<li><a href='navomatic.html'>Navomatic</a> - Automatic navigation using Borders and Links</li>
+<li><a href="navomatic.html">Navomatic</a> - Automatic navigation using Borders and Links</li>
-<li><a href='guestbook.html'>GuestBook</a> - A tiny blogger demonstrating ListViews and Forms</li>
+<li><a href="guestbook.html">GuestBook</a> - A tiny blogger demonstrating ListViews and Forms</li>
-<li><a href='dropdownchoice.html'>Using DropDownChoice</a> - A short example explaining the DropDownChoice component</li>
+<li><a href="dropdownchoice.html">Using DropDownChoice</a> - A short example explaining the DropDownChoice component</li>
-<li><a href='markupinheritance.html'>Markup Inheritance</a> - A short example explaining markup inheritance</li>
+<li><a href="markupinheritance.html">Markup Inheritance</a> - A short example explaining markup inheritance</li>
-<li><a href='ajaxcounter.html'>Ajax Counter</a> - A short example explaining Wicket’s Ajax features building a counter.</li>
+<li><a href="ajaxcounter.html">Ajax Counter</a> - A short example explaining Wicketâs Ajax features building a counter.</li>
-<li><a href='usingfragments.html'>Using Fragments</a> - A short example explaining Wicket’s fragments feature. Fragments are a type of inline panels.</li>
+<li><a href="usingfragments.html">Using Fragments</a> - A short example explaining Wicketâs fragments feature. Fragments are a type of inline panels.</li>
</ul>
</div>
<div id="clearer"></div>
Modified: wicket/common/site/trunk/_site/learn/examples/markupinheritance.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/markupinheritance.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/markupinheritance.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/markupinheritance.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -176,21 +176,21 @@
<h1>Creating layouts using markup inheritance</h1>
<p>This markup inheritance example show you how to create reusable page layouts and panel layouts.</p>
-<p><a href='http://wicket.apache.org/screencasts/ApacheWicket_MarkupInheritence.avi'>Watch the Screencast</a></p>
+<p><a href="http://wicket.apache.org/screencasts/ApacheWicket_MarkupInheritence.avi">Watch the Screencast</a></p>
<p>In all the Wicket examples, you have to put all files in the same package directory. This means putting the markup files and the java files next to one another. It is possible to alter this behavior, but that is beyond the scope of this example. The only exception is the obligatory <code>web.xml</code> file which should reside in the <code>WEB-INF/</code> directory of your web application root folder.</p>
-<p>In this example we assume you already have read and understood the other examples which give you information on the structure and nature of Wicket applications. Specifically read and understand the <a href='helloworld.html'>Hello, World example</a>.</p>
+<p>In this example we assume you already have read and understood the other examples which give you information on the structure and nature of Wicket applications. Specifically read and understand the <a href="helloworld.html">Hello, World example</a>.</p>
-<h2 id='page_layout'>Page layout</h2>
+<h2 id="page_layout">Page layout</h2>
<p>In the next figure we show a standard strategy for laying out a page. A standard header, the main content body and a standard footer.</p>
-<p><img src='markupinheritance1.png' alt='Markup inheritance diagram' /></p>
+<p><img src="markupinheritance1.png" alt="Markup inheritance diagram" /></p>
<p>In Wicket you can achieve this using different strategies. This article focuses on one strategy: markup inheritance.</p>
-<h2 id='what_is_markup_inheritance'>What is markup inheritance?</h2>
+<h2 id="what_is_markup_inheritance">What is markup inheritance?</h2>
<p>In Java you can extend classes. This same concept has been fitted into the markup parsing of Java. Markup containers that have files associated (page and panels) can inherit the markup of their super containers.</p>
@@ -228,11 +228,11 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<p>Here you can see that the <code><wicket:child /></code> tag has been expanded, and its contents filled with exactly the markup between the <code><wicket:extend></code> tags. If you want to get rid of the special Wicket tags, you can disable that on the markup settings (<a href='http://wicketframework.org/api/wicket/settings/IMarkupSettings'>IMarkupSettings</a>).</p>
+<p>Here you can see that the <code><wicket:child /></code> tag has been expanded, and its contents filled with exactly the markup between the <code><wicket:extend></code> tags. If you want to get rid of the special Wicket tags, you can disable that on the markup settings (<a href="http://wicketframework.org/api/wicket/settings/IMarkupSettings">IMarkupSettings</a>).</p>
-<h2 id='implementing_the_basepage'>Implementing the BasePage</h2>
+<h2 id="implementing_the_basepage">Implementing the BasePage</h2>
-<p>Now that we have seen the basics for markup inheritance, we can take a look at the example at hand. Let’s first create the base page.</p>
+<p>Now that we have seen the basics for markup inheritance, we can take a look at the example at hand. Letâs first create the base page.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>wicket</span><span class='o'>.</span><span class='na'>quickstart</span><span class='o'>;</span>
<span class='kn'>import</span> <span class='nn'>wicket.markup.html.WebPage</span><span class='o'>;</span>
@@ -247,7 +247,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<p>The two links should go into the header, and the footer in the footer of the page. Note that the abstract keyword isn’t required, but considered a good practise. Now let’s take a look at the markup for the BasePage</p>
+<p>The two links should go into the header, and the footer in the footer of the page. Note that the abstract keyword isnât required, but considered a good practise. Now letâs take a look at the markup for the BasePage</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
<span class='nt'><body></span>
@@ -274,11 +274,11 @@
<li><code><div id="footer">...</div></code></li>
</ol>
-<p>Note that these aren’t Wicket components, just plain markup. We could have made them components, such as a <code>Panel</code> but for brevity we keep it this way. Now that we have the <code>BasePage</code> finished, we can implement the two subclasses to finish this example.</p>
+<p>Note that these arenât Wicket components, just plain markup. We could have made them components, such as a <code>Panel</code> but for brevity we keep it this way. Now that we have the <code>BasePage</code> finished, we can implement the two subclasses to finish this example.</p>
-<h2 id='implementing_the_sub_pages'>Implementing the sub pages</h2>
+<h2 id="implementing_the_sub_pages">Implementing the sub pages</h2>
-<p>We need to build two pages: <code>Page1</code> and <code>Page2</code>. Each page needs its own markup file and Java class. Let’s first implement <code>Page1</code>.</p>
+<p>We need to build two pages: <code>Page1</code> and <code>Page2</code>. Each page needs its own markup file and Java class. Letâs first implement <code>Page1</code>.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>wicket</span><span class='o'>.</span><span class='na'>quickstart</span><span class='o'>;</span>
<span class='kn'>import</span> <span class='nn'>wicket.markup.html.basic.Label</span><span class='o'>;</span>
@@ -289,7 +289,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<p>In this example you see that we add a new label component to the page: <code>label1</code>. This component is only available for <code>Page1</code>, as such <code>Page2</code> can define its own component hierarchy. Let’s take a look at the markup for <code>Page1</code>:</p>
+<p>In this example you see that we add a new label component to the page: <code>label1</code>. This component is only available for <code>Page1</code>, as such <code>Page2</code> can define its own component hierarchy. Letâs take a look at the markup for <code>Page1</code>:</p>
<div class='highlight'><pre><code class='java'><span class='o'><</span><span class='n'>html</span><span class='o'>></span>
<span class='o'><</span><span class='n'>head</span><span class='o'>></</span><span class='n'>head</span><span class='o'>></span>
<span class='o'><</span><span class='n'>body</span><span class='o'>></span>
@@ -302,7 +302,7 @@
</code></pre></div>
<p>Here you see that we added the <code>Label</code> component in the markup between the <code><wicket:extend></code> tags. If we were to add the component outside those tags, Wicket will not be able to render the component in the final page.</p>
-<p>Now, let’s do the same for <code>Page2</code>.</p>
+<p>Now, letâs do the same for <code>Page2</code>.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>wicket</span><span class='o'>.</span><span class='na'>quickstart</span><span class='o'>;</span>
<span class='kn'>import</span> <span class='nn'>wicket.markup.html.basic.Label</span><span class='o'>;</span>
@@ -324,13 +324,13 @@
</code></pre></div>
<p>In <code>Page2</code> you see that we have a different component structure (<code>label2</code> instead of <code>label1</code>), and as such that the pages are quite different.</p>
-<p>If you paste this code into a Wicket quickstart application, you can see it immediately working (don’t forget to set the homepage to <code>Page1</code> or <code>Page2</code>).</p>
+<p>If you paste this code into a Wicket quickstart application, you can see it immediately working (donât forget to set the homepage to <code>Page1</code> or <code>Page2</code>).</p>
-<h2 id='conclusion'>Conclusion</h2>
+<h2 id="conclusion">Conclusion</h2>
<p>With markup inheritance you can get a standard layout for your application without too much hassle. It follows the natural inheritance strategy for Java code and makes encapsulation of your component hierarchy possible.</p>
-<p>In this example we haven’t touched on the other possible features of markup inheritance:</p>
+<p>In this example we havenât touched on the other possible features of markup inheritance:</p>
<ul>
<li>contributing to the <code><head></code> section from your sub pages</li>
Modified: wicket/common/site/trunk/_site/learn/examples/navomatic.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/navomatic.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/navomatic.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/navomatic.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -180,15 +180,15 @@
<p>The link in the navigation to the current page is automatically turned into italic text to indicate to the user what page they are on. The first screen capture shows the Page1 page with the Page1 link in italics.</p>
-<p><img src='navomatic1.png' alt='Figure 1' /></p>
+<p><img src="navomatic1.png" alt="Figure 1" /></p>
<p>When you click on the Page2 link, you get the following screen.</p>
-<p><img src='navomatic2.png' alt='Figure 2' /></p>
+<p><img src="navomatic2.png" alt="Figure 2" /></p>
<p>As you can see, Page1 has no special style anymore, and Page2 is now displayed in italics. Also the message box shows that we are viewing Page2 instead of Page1.</p>
-<h2 id='navigation_component'>Navigation component</h2>
+<h2 id="navigation_component">Navigation component</h2>
<p>To create a reusable navigation component we are going to use a <code>org.apache.wicket.markup.html.border.Border</code> component. From the Border Javadoc:</p>
@@ -196,11 +196,11 @@
<p>A border component has associated markup which is drawn and determines placement of any markup and/or components nested within the border component.</p>
</blockquote>
-<p>The portion of the border’s associated markup file which is to be used in rendering the border is denoted by a <code><wicket:border></code> tag. The children of the border component instance are then inserted into this markup, replacing the first <code><wicket:body/></code> tag in the border’s associated markup.</p>
+<p>The portion of the borderâs associated markup file which is to be used in rendering the border is denoted by a <code><wicket:border></code> tag. The children of the border component instance are then inserted into this markup, replacing the first <code><wicket:body/></code> tag in the borderâs associated markup.</p>
<p>For example, here is markup for a simple Border subclass, a usage of that border, and the markup which would be output on rendering:</p>
-<h3 id='border_markup'>Border markup</h3>
+<h3 id="border_markup">Border markup</h3>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><body></span>
<span class='nt'><wicket:border></span>
@@ -209,7 +209,7 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<h3 id='border_usage'>Border usage</h3>
+<h3 id="border_usage">Border usage</h3>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><body></span>
<span class='nt'><span</span> <span class='na'>wicket:id =</span><span class='err'> </span><span class='s'>"myBorder"</span><span class='nt'>></span>
@@ -218,16 +218,16 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<h3 id='rendered_markup'>Rendered markup</h3>
+<h3 id="rendered_markup">Rendered markup</h3>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><body></span>
First Middle Last
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<p>In other words, the markup around the <code><wicket:body/></code> tag in the border component is sort of “wrapped around” the body of the <code><span></code> tag where the border is used. This seems simple in this example, but keep in mind that nested components and even nested borders can appear anywhere in either markup file. This can be used to create quite complex effects with relatively little code.</p>
+<p>In other words, the markup around the <code><wicket:body/></code> tag in the border component is sort of âwrapped aroundâ the body of the <code><span></code> tag where the border is used. This seems simple in this example, but keep in mind that nested components and even nested borders can appear anywhere in either markup file. This can be used to create quite complex effects with relatively little code.</p>
-<h3 id='navomaticapplicationjava'>NavomaticApplication.java</h3>
+<h3 id="navomaticapplicationjava">NavomaticApplication.java</h3>
<p>Just as in the Hello World! example, we need to define our application. In this case, we set Page1 to be our home page.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>org</span><span class='o'>.</span><span class='na'>apache</span><span class='o'>.</span><span class='na'>wicket</span><span class='o'>.</span><span class='na'>examples</span><span class='o'>.</span><span class='na'>navomatic</span><span class='o'>;</span>
@@ -243,7 +243,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h3 id='page1java'>Page1.java</h3>
+<h3 id="page1java">Page1.java</h3>
<p>The Page1 Java and HTML files look like this:</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>wicket</span><span class='o'>.</span><span class='na'>examples</span><span class='o'>.</span><span class='na'>navomatic</span><span class='o'>;</span>
@@ -256,7 +256,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h3 id='page1html'>Page1.html</h3>
+<h3 id="page1html">Page1.html</h3>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><body></span>
<span class='nt'><span</span> <span class='na'>wicket:id =</span><span class='err'> </span><span class='s'>"navomaticBorder"</span><span class='nt'>></span>
@@ -265,18 +265,18 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<p>Notice that the NavomaticBorder component is attached to the <code><span></code> tag because the name of the component in the Java code is “navomaticBorder” and the <code><span></code> tag’s wicket:id attribute is set to “navomaticBorder”. Because the two names match, Wicket associates the NavomaticBorder Java component with the <code><span></code> tag.</p>
+<p>Notice that the NavomaticBorder component is attached to the <code><span></code> tag because the name of the component in the Java code is ânavomaticBorderâ and the <code><span></code> tagâs wicket:id attribute is set to ânavomaticBorderâ. Because the two names match, Wicket associates the NavomaticBorder Java component with the <code><span></code> tag.</p>
-<h3 id='page2java'>Page2.java</h3>
+<h3 id="page2java">Page2.java</h3>
-<p>The Page2 Java and HTML files look almost identical (and we’ll omit the sources for Page3 altogether because it follows the same pattern):</p>
+<p>The Page2 Java and HTML files look almost identical (and weâll omit the sources for Page3 altogether because it follows the same pattern):</p>
<div class='highlight'><pre><code class='java'><span class='kd'>public</span> <span class='kd'>class</span> <span class='nc'>Page2</span> <span class='kd'>extends</span> <span class='n'>WebPage</span> <span class='o'>{</span>
<span class='kd'>public</span> <span class='nf'>Page2</span><span class='o'>()</span> <span class='o'>{</span>
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>NavomaticBorder</span><span class='o'>(</span><span class='s'>"navomaticBorder"</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h3 id='page2html'>Page2.html</h3>
+<h3 id="page2html">Page2.html</h3>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><body></span>
<span class='nt'><span</span> <span class='na'>wicket:id =</span><span class='err'> </span><span class='s'>"navomaticBorder"</span><span class='nt'>></span>
@@ -285,7 +285,7 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<h3 id='navomaticborderjava'>NavomaticBorder.java</h3>
+<h3 id="navomaticborderjava">NavomaticBorder.java</h3>
<p>So how does NavomaticBorder work? Glad you asked. The Java code below simply adds the two BoxBorder components you see. These components are nested borders which each draw a thin black line around their contents. The rest of the magic is in the NavomaticBorder markup.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>wicket</span><span class='o'>.</span><span class='na'>examples</span><span class='o'>.</span><span class='na'>navomatic</span><span class='o'>;</span>
@@ -302,7 +302,7 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<h3 id='navomaticborderhtml'>NavomaticBorder.html</h3>
+<h3 id="navomaticborderhtml">NavomaticBorder.html</h3>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><body></span>
<span class='nt'><wicket:border></span>
@@ -333,13 +333,13 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<p>Notice that the markup above encloses the entire contents of the markup file’s <code><body></code> with a <code><wicket:border></code> tag, as we described earlier. This lets the NavomaticBorder know how much of its markup to use when it wraps itself around the markup it finds in the context where it is used. Notice also the <code><wicket:body/></code> marker which designates where to put whatever is found inside the tag at the use context.</p>
+<p>Notice that the markup above encloses the entire contents of the markup fileâs <code><body></code> with a <code><wicket:border></code> tag, as we described earlier. This lets the NavomaticBorder know how much of its markup to use when it wraps itself around the markup it finds in the context where it is used. Notice also the <code><wicket:body/></code> marker which designates where to put whatever is found inside the tag at the use context.</p>
-<p>Next, notice that the navigation links and the border’s <code><wicket:body/></code> are both enclosed in <code><span></code> tags which have wicket:id attributes that associate those tags with the BoxBorder components added in the NavomaticBorder constructor. These nested border components will each draw a thin black line around their contents.</p>
+<p>Next, notice that the navigation links and the borderâs <code><wicket:body/></code> are both enclosed in <code><span></code> tags which have wicket:id attributes that associate those tags with the BoxBorder components added in the NavomaticBorder constructor. These nested border components will each draw a thin black line around their contents.</p>
<p>Finally, the <code><wicket:link></code> tag is used to mark the links in the navigation as automatic links. Ordinarily, you would need to create link components and attach them to your page manually, but anchor links that are marked as automatic are parsed and hooked up to link components for you, as appropriate. The italicizing behavior is also automatic. Since Wicket knows which page is current, it removes the anchor link tag for any link that points to the current page (since the link would be useless) and italicizes the link text.</p>
-<h3 id='webxml'>web.xml</h3>
+<h3 id="webxml">web.xml</h3>
<p>In order to get this application up and running, we need to register the application with the Wicket servlet in the web.xml file. The following sections need to be added to the web.xml in the WEB-INF folder.</p>
<div class='highlight'><pre><code class='xml'><span class='nt'><servlet></span>
Modified: wicket/common/site/trunk/_site/learn/examples/usingfragments.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/usingfragments.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/usingfragments.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/usingfragments.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">Wicket 1.5</a>
@@ -174,15 +174,15 @@
<div id="contentbody">
<h1>Using Fragments</h1>
- <p>This example shows you how to use fragments (Wicket 1.2 feature) to lessen the burden on extra markup files. Fragments are ‘inline panels’ and are a quick way of using panel type components in pages without having to create a <code>Panel</code> markup file and class.</p>
+ <p>This example shows you how to use fragments (Wicket 1.2 feature) to lessen the burden on extra markup files. Fragments are âinline panelsâ and are a quick way of using panel type components in pages without having to create a <code>Panel</code> markup file and class.</p>
<p>In all the Wicket examples, you have to put all files in the same package directory. This means putting the markup files and the java files next to one another. It is possible to alter this behavior, but that is beyond the scope of this example. The only exception is the obligatory <code>web.xml</code> file which should reside in the <code>WEB-INF/</code> directory of your web application root folder.</p>
-<p>In this example we assume you already have read and understood the other examples which give you information on the structure and nature of Wicket applications. Specifically read and understand the <a href='helloworld.html'>Hello, World example</a>.</p>
+<p>In this example we assume you already have read and understood the other examples which give you information on the structure and nature of Wicket applications. Specifically read and understand the <a href="helloworld.html">Hello, World example</a>.</p>
-<h2 id='creating_a_fragment'>Creating a Fragment</h2>
+<h2 id="creating_a_fragment">Creating a Fragment</h2>
-<p>First things first, let’s create a page that we can add our fragments to. We will add a Loop that will repeat markup and choose a different Fragment for each item in the loop.</p>
+<p>First things first, letâs create a page that we can add our fragments to. We will add a Loop that will repeat markup and choose a different Fragment for each item in the loop.</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
<span class='nt'><body></span>
@@ -214,9 +214,9 @@
</code></pre></div>
<p>The Loop will render 5 items, and the <code>populateItem</code> method will be called for each item. In each item we construct a fragment identifier that corresponds to the identifier in the <code><wicket:fragment></code>. The <code>Fragment</code> constructor takes the identifier of the markup it needs to attach to, and the fragment identifier telling it where to find the specific markup in the file.</p>
-<h2 id='adding_components_to_fragments'>Adding components to fragments</h2>
+<h2 id="adding_components_to_fragments">Adding components to fragments</h2>
-<p>In the previous example we just showed different markup for each fragment, but you can add components to the fragments as well. Let’s add a label to fragment 1.</p>
+<p>In the previous example we just showed different markup for each fragment, but you can add components to the fragments as well. Letâs add a label to fragment 1.</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
<span class='nt'><body></span>
@@ -228,7 +228,7 @@
<span class='nt'></body></span>
<span class='nt'></html></span>
</code></pre></div>
-<p>In order to add the component to the first fragment we’ll introduce a subclass for fragment one to encapsulate the component.</p>
+<p>In order to add the component to the first fragment weâll introduce a subclass for fragment one to encapsulate the component.</p>
<div class='highlight'><pre><code class='java'><span class='kn'>package</span> <span class='n'>wicket</span><span class='o'>.</span><span class='na'>quickstart</span><span class='o'>;</span>
<span class='kn'>import</span> <span class='nn'>wicket.markup.html.basic.Label</span><span class='o'>;</span>
@@ -259,9 +259,9 @@
<span class='o'>}</span>
<span class='o'>}</span>
</code></pre></div>
-<p>The class <code>Fragment1</code> adds the label to itself. In the loop’s <code>populateItem</code> we alternate the fragments type between <code>Fragment</code> and <code>Fragment1</code>. This means that in the final page on one line you’ll see <code>"panel 1 Hello, World!"</code> and on the other line just <code>"panel 2"</code>.</p>
+<p>The class <code>Fragment1</code> adds the label to itself. In the loopâs <code>populateItem</code> we alternate the fragments type between <code>Fragment</code> and <code>Fragment1</code>. This means that in the final page on one line youâll see <code>"panel 1 Hello, World!"</code> and on the other line just <code>"panel 2"</code>.</p>
-<h2 id='summary'>Summary</h2>
+<h2 id="summary">Summary</h2>
<p>Fragments make a quick way to add encapsulated components without having to resort to setting the visibility flag on a markup container. For fragments we introduced a new Wicket tag: <code><wicket:fragment></code>.</p>
</div>
Modified: wicket/common/site/trunk/_site/learn/ides.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/ides.html?rev=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/ides.html (original)
+++ wicket/common/site/trunk/_site/learn/ides.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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 title='NetBeans Community Wiki' href='http://wiki.netbeans.org/MavenBestPractices'>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 title='IDEA Web Help' href='http://www.jetbrains.com/idea/webhelp/maven.html'>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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/index.html (original)
+++ wicket/common/site/trunk/_site/learn/index.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/authroles.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/authroles.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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,42 +230,46 @@
<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> - JAAS inspired, principal based security framework</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>
</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.12.0<span class='nt'></version></span>
+ <span class='nt'><version></span>6.13.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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/datetime.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/datetime.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/devutils.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/devutils.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/extensions.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/extensions.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/guice.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/guice.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/index.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/index.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/ioc.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/ioc.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/jmx.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/jmx.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/spring.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/spring.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/projects/velocity.html (original)
+++ wicket/common/site/trunk/_site/learn/projects/velocity.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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.12.0<span class='nt'></version></span>
+ <span class='nt'><version></span>6.13.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=1557758&r1=1557757&r2=1557758&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/meet/blogs.html (original)
+++ wicket/common/site/trunk/_site/meet/blogs.html Mon Jan 13 16:02:24 2014
@@ -92,7 +92,7 @@
</h5>
<ul>
<li>
- <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.12.0">Wicket 6.12</a>
+ <a href="http://www.apache.org/dyn/closer.cgi/wicket/6.13.0">Wicket 6.13</a>
</li>
<li>
<a href="http://www.apache.org/dyn/closer.cgi/wicket/1.5.10">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>