You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by mg...@apache.org on 2014/07/19 14:14:04 UTC
svn commit: r1611901 [8/10] - in /wicket/common/site/trunk: _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/05/24/ _site...
Modified: wicket/common/site/trunk/_site/learn/books/prowicket.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/books/prowicket.html?rev=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/books/prowicket.html (original)
+++ wicket/common/site/trunk/_site/learn/books/prowicket.html Sat Jul 19 12:14:02 2014
@@ -189,21 +189,21 @@
<h1>Books â Pro Wicket</h1>
<p>Pro Wicket, written by by Karthik Gurumurthy, is the first book about Wicket, and covers Wicket 1.2. It was published by Apress in September 2006.</p>
-<h2 id='description'>Description</h2>
+<h2 id="description">Description</h2>
<p>Wicket is an open source, component-oriented (POJOs-based), lightweight Java web application development framework that brings the Java Swing event-based programming model to web development. Wicket pages can be mocked up, previewed, and later revised using standard WYSIWYG HTML design tools.</p>
<p>Wicket provides stateful components, thereby improving productivity. It has an architecture and rich component suite that aims to bring back the object orientation and, more importantly, the fun that is missing from the Java web development space. With the impending 1.2 release, Wicket is set for wider adoption.</p>
-<p>Pro Wicket gets you up and running quickly with this framework. You’ll learn how to configure Wicket, then gradually gain exposure to the “Wicket way” of addressing web development requirements. You’ll want to pick up a copy because it</p>
+<p>Pro Wicket gets you up and running quickly with this framework. Youâll learn how to configure Wicket, then gradually gain exposure to the âWicket wayâ of addressing web development requirements. Youâll want to pick up a copy because it</p>
<p>Is the first book to cover the Wicket framework with Spring integration and Ajax features Demonstrates all major wicket capabilities through simple examples Covers important aspects like Wicket-Spring integration and Ajax support</p>
-<h2 id='about_the_author'>About the author</h2>
+<h2 id="about_the_author">About the author</h2>
<p>Karthik Gurumurthy has been associated with the IT industry for more than six years now and has employed open source libraries to solve business problems. Karthik also has the experience of having documented a popular open source project: XDoclet2. He has been having a great time with Wicket since day one of adoption and would like to let others know how Wicket succeeds in bringing back the fun that has been missing in the Java web development space. He also contributed to the Wicket project through the Wicket-Spring integration module using Jakarta Commons Attributes.</p>
-<h2 id='book_details'>Book details</h2>
+<h2 id="book_details">Book details</h2>
<p>Title Pro Wicket Author Karthik Gurumurthy Version covered Wicket 1.2 URL Pro Wicket Hardcover 328 pages Publisher Apress Date September 7, 2006 Language English ISBN-10 1590597222 ISBN-13 978-1590597224 Buy Amazon Apress</p>
</div>
Modified: wicket/common/site/trunk/_site/learn/books/wia.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/books/wia.html?rev=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/books/wia.html (original)
+++ wicket/common/site/trunk/_site/learn/books/wia.html Sat Jul 19 12:14:02 2014
@@ -189,19 +189,19 @@
<h1>Wicket in Action</h1>
<p>Wicket in Action is written by Martijn Dashorst and Eelco Hillenius and is published by Manning. The book is currently in the final stages of production and will soon be available as a hard copy. Early access to the manuscript is available from the publishers site.</p>
-<h3 id='description'>Description</h3>
+<h3 id="description">Description</h3>
<p>There are dozens of Java frameworks out there, but most of them require you to learn special coding techniques and new, often rigid, patterns of development. Wicket is different. As a component-based Web application framework, Wicket lets you build maintainable enterprise-grade web applications using the power of plain old Java objects (POJOs), HTML, Ajax, Spring, Hibernate and Maven. Wicket automatically manages state at the component level, which means no more awkward HTTPSession objects. Its elegant programming model enables you to write rich web applications quickly.</p>
-<p>Wicket in Action is the authoritative, comprehensive guide for Java developers building Wicket-based Web applications. This book starts with an introduction to Wicket’s structure and components, and moves quickly into examples of Wicket at work. Written by two of the project’s earliest and most authoritative experts, this book shows you both the “how-to” and the “why” of Wicket. As you move through the book, you’ll learn to use and customize Wicket components, how to interact with other technologies like Spring and Hibernate, and how to build rich, Ajax-driven features into your applications.</p>
+<p>Wicket in Action is the authoritative, comprehensive guide for Java developers building Wicket-based Web applications. This book starts with an introduction to Wicketâs structure and components, and moves quickly into examples of Wicket at work. Written by two of the projectâs earliest and most authoritative experts, this book shows you both the âhow-toâ and the âwhyâ of Wicket. As you move through the book, youâll learn to use and customize Wicket components, how to interact with other technologies like Spring and Hibernate, and how to build rich, Ajax-driven features into your applications.</p>
-<h3 id='authors'>Authors</h3>
+<h3 id="authors">Authors</h3>
<p>Martijn Dashorst is a software engineer with over 10 years of experience in software development. He has been actively involved in the Wicket project since it was open sourced, and has presented Wicket as a speaker at numerous conferences, including JavaOne and JavaPolis.</p>
-<p>Eelco Hillenius is an experienced software developer who has been part of Wicket’s core team almost from the start. He works for Teachscape where he helping to build the next elearning platform. A Dutch native, he currently lives in Seattle.</p>
+<p>Eelco Hillenius is an experienced software developer who has been part of Wicketâs core team almost from the start. He works for Teachscape where he helping to build the next elearning platform. A Dutch native, he currently lives in Seattle.</p>
-<h3 id='book_details'>Book details</h3>
+<h3 id="book_details">Book details</h3>
</div>
<div id="clearer"></div>
<div id="footer"><span>
Modified: wicket/common/site/trunk/_site/learn/books/wicket-jp.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/books/wicket-jp.html?rev=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/books/wicket-jp.html (original)
+++ wicket/common/site/trunk/_site/learn/books/wicket-jp.html Sat Jul 19 12:14:02 2014
@@ -191,15 +191,15 @@
<p>This is the only book in Japanese covering Apache Wicket. It discusses Wicket 1.4.</p>
-<h2 id='description'>Description</h2>
+<h2 id="description">Description</h2>
<p>After all just Java and HTML. To complex applications using Ajax, XML created without light. Recover the object-oriented server-side. Apache Wicket 1.4-RC2 support.</p>
-<h2 id='about_the_author'>About the author</h2>
+<h2 id="about_the_author">About the author</h2>
-<p>Yano Tsutomu Born in Osaka in 1973. He joined the system development company, is currently working as a freelance programmer and retired. In 2008 Wicket User Group “Wicket-ja” up and, to the present (this data is published at the time was that this book was published.)</p>
+<p>Yano Tsutomu Born in Osaka in 1973. He joined the system development company, is currently working as a freelance programmer and retired. In 2008 Wicket User Group âWicket-jaâ up and, to the present (this data is published at the time was that this book was published.)</p>
-<h2 id='book_details'>Book details</h2>
+<h2 id="book_details">Book details</h2>
<p>Paperback: 431 pages Publisher: Hidekazu system (2009/03) ISBN-10: 4798022217 ISBN-13: 978-4798022215 Release Date: 2009/03</p>
</div>
Modified: wicket/common/site/trunk/_site/learn/examples/ajaxcounter.html
URL: http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/learn/examples/ajaxcounter.html?rev=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/ajaxcounter.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/ajaxcounter.html Sat Jul 19 12:14:02 2014
@@ -187,15 +187,15 @@
<div id="contentbody">
<h1>Ajax Counter</h1>
- <p>This example shows you how to use Wicket’s Ajax behaviors and components by building a simple counter that updates through Ajax link clicks.</p>
+ <p>This example shows you how to use Wicketâs Ajax behaviors and components by building a simple counter that updates through Ajax link clicks.</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='counter_page'>Counter page</h2>
+<h2 id="counter_page">Counter page</h2>
-<p>First we’ll create a page that just counts the number of times a link has been clicked. In the following markup you’ll see a link and a label.</p>
+<p>First weâll create a page that just counts the number of times a link has been clicked. In the following markup youâll see a link and a label.</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
<span class='nt'><body></span>
@@ -205,9 +205,8 @@
<span class='nt'></p></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
-<p>The link component will refresh the page and the label will replace the text ‘nr of times’ with the count. Take a look at the following Java file to see how it works on the Java side:</p>
+</code></pre></div>
+<p>The link component will refresh the page and the label will replace the text ânr of timesâ with the count. Take a look at the following Java file to see how it works on the Java side:</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.Component</span><span class='o'>;</span>
@@ -232,17 +231,16 @@
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>Label</span><span class='o'><</span><span class='n'>Integer</span><span class='o'>>(</span><span class='s'>"counter"</span><span class='o'>,</span> <span class='n'>model</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
+</code></pre></div>
<p>In this class we created a <code>Model</code> subclass that increases its counter everytime the <code>getObject</code> method gets called, and returns its value. We set this model on the label component, so that each time the label gets rendered the counter gets increased.</p>
-<p>The link doesn’t do anything, just listen to the requests and update the page. If you run this code in your application (download the Quickstart project and copy/paste the code in the homepage for a quick experience).</p>
+<p>The link doesnât do anything, just listen to the requests and update the page. If you run this code in your application (download the Quickstart project and copy/paste the code in the homepage for a quick experience).</p>
-<p>The page gets fully refreshed with each link click. That is not very web 2.0, so let’s make it more modern by adding some Ajax stuff.</p>
+<p>The page gets fully refreshed with each link click. That is not very web 2.0, so letâs make it more modern by adding some Ajax stuff.</p>
-<h2 id='adding_ajax'>Adding Ajax</h2>
+<h2 id="adding_ajax">Adding Ajax</h2>
-<p>To make this a more modern UI we’ll have to change a couple of things. First we need to make the link an Ajax link. Wicket provides several types of Ajax links, but the best one for our purposes is the <code>AjaxFallbackLink</code>, as it provides a fallback to a normal request in case no Ajax is available.</p>
+<p>To make this a more modern UI weâll have to change a couple of things. First we need to make the link an Ajax link. Wicket provides several types of Ajax links, but the best one for our purposes is the <code>AjaxFallbackLink</code>, as it provides a fallback to a normal request in case no Ajax is available.</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.Component</span><span class='o'>;</span>
@@ -269,9 +267,8 @@
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>Label</span><span class='o'><</span><span class='n'>Integer</span><span class='o'>>(</span><span class='s'>"counter"</span><span class='o'>,</span> <span class='n'>model</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<p>As you can see, the <code>Link</code> has been replaced with the <code>AjaxFallbackLink</code>, and the <code>onClick</code> method now takes a new argument: the <code>AjaxRequestTarget</code>. If you want a component to be updated in the Ajax request, you’ll have to add them to the target. So let’s alter the file to make it possible to add the label to the request target.</p>
+</code></pre></div>
+<p>As you can see, the <code>Link</code> has been replaced with the <code>AjaxFallbackLink</code>, and the <code>onClick</code> method now takes a new argument: the <code>AjaxRequestTarget</code>. If you want a component to be updated in the Ajax request, youâll have to add them to the target. So letâs alter the file to make it possible to add the label to the request target.</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.Component</span><span class='o'>;</span>
@@ -302,17 +299,16 @@
<span class='n'>add</span><span class='o'>(</span><span class='n'>label</span><span class='o'>);</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<p>We’ve moved the instantiation of the label to the beginning of the page constructor and made a local, final variable. This way we can reference the label in the event handler of the link component.</p>
+</code></pre></div>
+<p>Weâve moved the instantiation of the label to the beginning of the page constructor and made a local, final variable. This way we can reference the label in the event handler of the link component.</p>
-<p>We also had to call <code>setOutputMarkupId(true)</code> on the label to be able to update the component when the request is returned to the client browser. If we don’t, Wicket will not know how to update the markup in the client.</p>
+<p>We also had to call <code>setOutputMarkupId(true)</code> on the label to be able to update the component when the request is returned to the client browser. If we donât, Wicket will not know how to update the markup in the client.</p>
-<p>If you put this code into your page’s class, then you’ll have a working Ajax updating counter.</p>
+<p>If you put this code into your pageâs class, then youâll have a working Ajax updating counter.</p>
-<h2 id='summary'>Summary</h2>
+<h2 id="summary">Summary</h2>
-<p>Working with Ajax and Wicket using the standard Wicket libraries doesn’t require a degree in JavaScript. Even better, you don’t necessarily need to update your markup file to work with Ajax. In this (simple) example we were able to add Ajax behavior to the page without touching the markup file.</p>
+<p>Working with Ajax and Wicket using the standard Wicket libraries doesnât require a degree in JavaScript. Even better, you donât necessarily need to update your markup file to work with Ajax. In this (simple) example we were able to add Ajax behavior to the page without touching the markup file.</p>
<p>The most important lesson here is that in order to update components using Ajax is that you need to add those components to the <code>AjaxRequestTarget</code> and that the components that are to be updated in that request, should have <code>setOutputMarkupId(true)</code>.</p>
</div>
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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/dropdownchoice.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/dropdownchoice.html Sat Jul 19 12:14:02 2014
@@ -187,11 +187,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>
@@ -213,9 +213,8 @@
<span class='c1'>// gets the managers from the database</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<h2 id='the_assign_manager_page'>The assign manager page</h2>
+</code></pre></div>
+<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>
@@ -240,8 +239,7 @@
<span class='nt'></form></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>This page has three components:</p>
<ul>
@@ -254,7 +252,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>
@@ -274,8 +272,7 @@
<span class='n'>form</span><span class='o'>.</span><span class='na'>add</span><span class='o'>(</span><span class='n'>ddc</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
+</code></pre></div>
<p>In this example you see that we add the <code>DropDownChoice</code> to the form, and provide it with 3 parameters. The first is the component identifier. The second is the item that needs to be updated, in this case the <code>managedBy</code> field of the <code>employee</code>. The third parameter is a <code>LoadableDetachableModel</code> that retrieves the list of available choices.</p>
<p>Note that the <code>DropDownChoice</code> component has many constructors, and that you need to read the JavaDoc documentation to pick the right one for you.</p>
@@ -293,11 +290,10 @@
<span class='nt'></select></span>
<span class='nt'></td></span>
<span class='nt'></tr></span>
-</code></pre>
-</div>
+</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>
@@ -308,14 +304,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>
@@ -324,9 +320,8 @@
<span class='n'>newEmployee</span><span class='o'>.</span><span class='na'>setManagedBy</span><span class='o'>(</span><span class='n'>manager</span><span class='o'>);</span>
<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>
+</code></pre></div>
+<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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/guestbook.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/guestbook.html Sat Jul 19 12:14:02 2014
@@ -189,11 +189,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 alt='Guestbook screenshot' src='guestbook.png' /></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>
@@ -233,9 +233,8 @@
<span class='k'>return</span> <span class='s'>"[Comment date = "</span> <span class='o'>+</span> <span class='n'>date</span> <span class='o'>+</span> <span class='s'>", text = "</span> <span class='o'>+</span> <span class='n'>text</span> <span class='o'>+</span> <span class='s'>"]"</span><span class='o'>;</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<h2 id='guestbookjava'>GuestBook.java</h2>
+</code></pre></div>
+<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>
@@ -335,15 +334,14 @@
<span class='n'>commentList</span><span class='o'>.</span><span class='na'>clear</span><span class='o'>();</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
+</code></pre></div>
<p>When the <code>CommentForm</code> is submitted, the <code>onSubmit()</code> method is called. Notice that nothing gets the value of the <code>TextArea</code> that was added in the <code>CommentForm</code> constructor. This is because the comment is the model and the third parameter to the <code>TextArea</code> constructor specified the property of the model to update. So all <code>onSubmit()</code> has to do is create a new comment from the model that was updated and add it to the comment list. When the page redraws, the new list will be rendered.</p>
<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>
@@ -379,11 +377,10 @@
<span class='nt'></wicket:remove></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
-<h2 id='guestbookapplicationjava'>GuestBookApplication.java</h2>
+</code></pre></div>
+<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>
@@ -398,9 +395,8 @@
<span class='k'>return</span> <span class='n'>GuestBook</span><span class='o'>.</span><span class='na'>class</span><span class='o'>;</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<h2 id='webxml'>web.xml</h2>
+</code></pre></div>
+<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>
@@ -411,8 +407,7 @@
<span class='nt'><param-value></span>org.apache.wicket.examples.guestbook.GuestBookApplication<span class='nt'></param-value></span>
<span class='nt'></init-param></span>
<span class='nt'></filter></span>
-</code></pre>
-</div>
+</code></pre></div>
</div>
<div id="clearer"></div>
<div id="footer"><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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/helloworld.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/helloworld.html Sat Jul 19 12:14:02 2014
@@ -193,7 +193,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>
@@ -210,11 +210,10 @@
<span class='k'>return</span> <span class='n'>HelloWorld</span><span class='o'>.</span><span class='na'>class</span><span class='o'>;</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
+</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>
@@ -223,23 +222,22 @@
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>Label</span><span class='o'>(</span><span class='s'>"message"</span><span class='o'>,</span> <span class='s'>"Hello World!"</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
+</code></pre></div>
<p>The Label is constructed using two parameters:</p>
<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,8 +245,7 @@
<span class='nt'><span</span> <span class='na'>wicket:id=</span><span class='s'>"message"</span><span class='nt'>></span>Message goes here<span class='nt'></span></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>In this file, you see two elements that need some attention:</p>
<ul>
@@ -263,7 +260,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>
@@ -286,15 +283,14 @@
<span class='nt'><url-pattern></span>/*<span class='nt'></url-pattern></span>
<span class='nt'></filter-mapping></span>
<span class='nt'></web-app></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>In this definition you see the Wicket filter defined, which handles all requests. In order to let Wicket know which application is available, only the applicationClassName filter parameter is needed.</p>
<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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/index.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/index.html Sat Jul 19 12:14:02 2014
@@ -187,24 +187,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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/markupinheritance.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/markupinheritance.html Sat Jul 19 12:14:02 2014
@@ -189,21 +189,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 alt='Markup inheritance diagram' src='markupinheritance1.png' /></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>
@@ -216,8 +216,7 @@
This is in the super markup.<span class='nt'><br></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>In this markup you see two sentences that surround the <code><wicket:child></code> tag. All markup in this file will remain when a sub class of this page is created, only the <code><wicket:child></code> tag will be replaced with the child markup. So if we look at the following markup:</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
@@ -229,8 +228,7 @@
This is in the child markup.<span class='nt'><br></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>we can see the markup that should be included in the parent. Only the markup between the <code><wicket:extend></code> tags is included in the final page. Take a look at the following markup which is the final markup when you would use this in a Wicket application.</p>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
@@ -242,13 +240,12 @@
This is in the super markup.<span class='nt'><br></span>
<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>
+</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>
-<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>
@@ -262,9 +259,8 @@
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>Label</span><span class='o'>(</span><span class='s'>"footer"</span><span class='o'>,</span> <span class='s'>"This is in the footer"</span><span class='o'>));</span>
<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>
+</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>
<div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
<span class='nt'><body></span>
@@ -280,8 +276,7 @@
<span class='nt'></div></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>In this markup file you see the specific basic layout: we have 3 div elements:</p>
<ol>
@@ -292,11 +287,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>
@@ -306,9 +301,8 @@
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>Label</span><span class='o'>(</span><span class='s'>"label1"</span><span class='o'>,</span> <span class='s'>"This is in the subclass Page1"</span><span class='o'>));</span>
<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>
+</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>
<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>
@@ -318,11 +312,10 @@
<span class='o'></</span><span class='nl'>wicket:</span><span class='n'>extend</span><span class='o'>></span>
<span class='o'></</span><span class='n'>body</span><span class='o'>></span>
<span class='o'></</span><span class='n'>html</span><span class='o'>></span>
-</code></pre>
-</div>
+</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>
@@ -332,8 +325,7 @@
<span class='n'>add</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>Label</span><span class='o'>(</span><span class='s'>"label2"</span><span class='o'>,</span> <span class='s'>"This is in the subclass Page2"</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div><div class='highlight'><pre><code class='html'><span class='nt'><html></span>
+</code></pre></div><div class='highlight'><pre><code class='html'><span class='nt'><html></span>
<span class='nt'><head></head></span>
<span class='nt'><body></span>
<span class='nt'><wicket:extend></span>
@@ -342,17 +334,16 @@
<span class='nt'></wicket:extend></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/navomatic.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/navomatic.html Sat Jul 19 12:14:02 2014
@@ -193,15 +193,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 alt='Figure 1' src='navomatic1.png' /></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 alt='Figure 2' src='navomatic2.png' /></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>
@@ -209,11 +209,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>
@@ -221,9 +221,8 @@
<span class='nt'></wicket:border></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
-<h3 id='border_usage'>Border usage</h3>
+</code></pre></div>
+<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>
@@ -231,19 +230,17 @@
<span class='nt'></span></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
-<h3 id='rendered_markup'>Rendered markup</h3>
+</code></pre></div>
+<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>
+</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>
-<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>
@@ -258,9 +255,8 @@
<span class='k'>return</span> <span class='n'>Page1</span><span class='o'>.</span><span class='na'>class</span><span class='o'>;</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<h3 id='page1java'>Page1.java</h3>
+</code></pre></div>
+<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>
@@ -272,9 +268,8 @@
<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='page1html'>Page1.html</h3>
+</code></pre></div>
+<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>
@@ -282,21 +277,19 @@
<span class='nt'></span></span>
<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>
+</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>
-<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>
+</code></pre></div>
+<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>
@@ -304,9 +297,8 @@
<span class='nt'></span></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
-<h3 id='navomaticborderjava'>NavomaticBorder.java</h3>
+</code></pre></div>
+<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>
@@ -322,9 +314,8 @@
<span class='n'>addToBorder</span><span class='o'>(</span><span class='k'>new</span> <span class='n'>BoxBorder</span><span class='o'>(</span><span class='s'>"bodyBorder"</span><span class='o'>));</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
-<h3 id='navomaticborderhtml'>NavomaticBorder.html</h3>
+</code></pre></div>
+<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>
@@ -354,15 +345,14 @@
<span class='nt'></wicket:border></span>
<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>
+</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>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>
@@ -378,8 +368,7 @@
<span class='nt'><servlet-name></span>NavomaticApplication<span class='nt'></servlet-name></span>
<span class='nt'><url-pattern></span>/app/*<span class='nt'></url-pattern></span>
<span class='nt'></servlet-mapping></span>
-</code></pre>
-</div>
+</code></pre></div>
</div>
<div id="clearer"></div>
<div id="footer"><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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/examples/usingfragments.html (original)
+++ wicket/common/site/trunk/_site/learn/examples/usingfragments.html Sat Jul 19 12:14:02 2014
@@ -187,15 +187,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>
@@ -206,8 +206,7 @@
<span class='nt'><wicket:fragment</span> <span class='na'>wicket:id=</span><span class='s'>"fragment2"</span><span class='nt'>></span>panel 2<span class='nt'></wicket:fragment></span>
<span class='nt'></body></span>
<span class='nt'></html></span>
-</code></pre>
-</div>
+</code></pre></div>
<p>As you can see in this markup file, we already took care of adding the fragment markup to the page in the <code><wicket:fragment></code> tags. Each fragment can contain its own markup and components. Those components need to be added to the Fragment instance in the Java file, just as you would do with a panel and web markup container.</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>
@@ -225,13 +224,12 @@
<span class='n'>add</span><span class='o'>(</span><span class='n'>loop</span><span class='o'>);</span>
<span class='o'>}</span>
<span class='o'>}</span>
-</code></pre>
-</div>
+</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>
@@ -242,9 +240,8 @@
<span class='nt'><wicket:fragment</span> <span class='na'>wicket:id=</span><span class='s'>"fragment2"</span><span class='nt'>></span>panel 2<span class='nt'></wicket:fragment></span>
<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>
+</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>
<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>
@@ -274,11 +271,10 @@
<span class='n'>add</span><span class='o'>(</span><span class='n'>loop</span><span class='o'>);</span>
<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>
+</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>
-<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=1611901&r1=1611900&r2=1611901&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/learn/ides.html (original)
+++ wicket/common/site/trunk/_site/learn/ides.html Sat Jul 19 12:14:02 2014
@@ -187,49 +187,46 @@
<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>
+</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>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>
-</code></pre>
-</div>
+</code></pre></div>
<p>If you want to go along with the Wicket way of code formatting you should import the Wicket code format profile into your workspace (Preferences->Java->Code Style->Formatter), found in:</p>
<div class='highlight'><pre><code class='console'><span class='go'><path-to-eclipse-workspace>/wicket-core/EclipseCodeFormat.xml</span>
-</code></pre>
-</div>
+</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>