This is why Tapestry provides an
opportunity to have page-specific message catalogs that contain messages for only
one page. We can also have component-specific method catalogs, as you will see in
the next chapter.
Right now, let's create a message catalog for the Start page. The trick is that in the
current version of Tapestry, message catalogs for pages should be placed under the
same structure of subdirectories under which page classes exist in their packages.
Say, if the fully qualified name of the Start page is com.packtpub.celebrities.
pages.Start, and so the page class can be found under the corresponding structure
of subdirectories (com\packtpub\celebrities\pages). Its message catalog,
to be successfully found by Tapestry, should be placed under the same structure
of subdirectories.
The easiest way to achieve this is to create a Start.properties file and place it
straight inside the com.packtpub.celebrities.pages package in your IDE??”the
same package that contains the source code of the Start page class.
In NetBeans, right-click on the mentioned package and select New | File/Folder??¦
In the dialog that opens, select Other for Categories and Empty File for File Types.
Pages:
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229