|
237 | 237 | <imagedata align="center" fileref="images/mvc.png" format="PNG" />
|
238 | 238 | </imageobject>
|
239 | 239 |
|
240 |
| - <caption><para>The requesting processing workflow in Spring Web MVC |
| 240 | + <caption><para>The request processing workflow in Spring Web MVC |
241 | 241 | (high level)</para></caption>
|
242 | 242 | </mediaobject></para>
|
243 | 243 |
|
@@ -843,7 +843,7 @@ public String findOwner(<emphasis role="bold">@PathVariable</emphasis>("ownerId"
|
843 | 843 | <programlisting language="java">@RequestMapping(value="/owners/{ownerId}/pets/{petId}", method=RequestMethod.GET)
|
844 | 844 | public String findPet(<emphasis role="bold">@PathVariable</emphasis> String ownerId, <emphasis
|
845 | 845 | role="bold">@PathVariable</emphasis> String petId, Model model) {
|
846 |
| - Owner owner = ownerService.findOwner(ownderId); |
| 846 | + Owner owner = ownerService.findOwner(ownerId); |
847 | 847 | Pet pet = owner.getPet(petId);
|
848 | 848 | model.addAttribute("pet", pet);
|
849 | 849 | return "displayPet";
|
@@ -3208,21 +3208,22 @@ public class SimpleController {
|
3208 | 3208 | </sidebar>
|
3209 | 3209 |
|
3210 | 3210 | <para>The strategy for generating a name after adding a
|
3211 |
| - <interfacename>Set</interfacename>, <interfacename>List</interfacename> |
3212 |
| - or array object is to peek into the collection, take the short class |
3213 |
| - name of the first object in the collection, and use that with |
3214 |
| - <literal>List</literal> appended to the name. Some examples will make |
3215 |
| - the semantics of name generation for collections clearer...</para> |
| 3211 | + <interfacename>Set</interfacename> or a <interfacename>List</interfacename> |
| 3212 | + is to peek into the collection, take the short class name of the first object |
| 3213 | + in the collection, and use that with <literal>List</literal> appended to the |
| 3214 | + name. The same applies to arrays although with arrays it is not necessary to |
| 3215 | + peek into the array contents. A few examples will make the semantics of name |
| 3216 | + generation for collections clearer:</para> |
3216 | 3217 |
|
3217 | 3218 | <itemizedlist>
|
3218 | 3219 | <listitem>
|
3219 |
| - <para>An <classname>x.y.User[]</classname> array with one or more |
| 3220 | + <para>An <classname>x.y.User[]</classname> array with zero or more |
3220 | 3221 | <classname>x.y.User</classname> elements added will have the name
|
3221 | 3222 | <literal>userList</literal> generated.</para>
|
3222 | 3223 | </listitem>
|
3223 | 3224 |
|
3224 | 3225 | <listitem>
|
3225 |
| - <para>An <classname>x.y.Foo[]</classname> array with one or more |
| 3226 | + <para>An <classname>x.y.Foo[]</classname> array with zero or more |
3226 | 3227 | <classname>x.y.User</classname> elements added will have the name
|
3227 | 3228 | <literal>fooList</literal> generated.</para>
|
3228 | 3229 | </listitem>
|
|
0 commit comments