You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by an...@apache.org on 2008/12/10 13:48:51 UTC
svn commit: r725072 - /tapestry/tapestry5/trunk/src/site/apt/cookbook/lib.apt
Author: andyhot
Date: Wed Dec 10 04:48:51 2008
New Revision: 725072
URL: http://svn.apache.org/viewvc?rev=725072&view=rev
Log:
typos
Modified:
tapestry/tapestry5/trunk/src/site/apt/cookbook/lib.apt
Modified: tapestry/tapestry5/trunk/src/site/apt/cookbook/lib.apt
URL: http://svn.apache.org/viewvc/tapestry/tapestry5/trunk/src/site/apt/cookbook/lib.apt?rev=725072&r1=725071&r2=725072&view=diff
==============================================================================
--- tapestry/tapestry5/trunk/src/site/apt/cookbook/lib.apt (original)
+++ tapestry/tapestry5/trunk/src/site/apt/cookbook/lib.apt Wed Dec 10 04:48:51 2008
@@ -161,7 +161,7 @@
Step 4: Configure the virtual folder
- Tapestry needs to know to where to search for your component class. This is accomplished in your library's IoC module class, by
+ Tapestry needs to know where to search for your component class. This is accomplished in your library's IoC module class, by
making a <contribution> to the ComponentClassResolver {{{../../tapestry-ioc/configuration.html}service configuration}}.
----
@@ -229,7 +229,7 @@
To handle this problem, you should map your library assets to a versioned folder. This can be accomplished using
another contribution from the HappyModule, this time to the ClasspathAssetAliasManager service
- whose configuration maps a virtual folder under neath /assets
+ whose configuration maps a virtual folder underneath /assets
to a package: