|
From: Stephane B. <ste...@be...> - 2004-06-09 08:09:21
|
Tomas Gustavsson wrote: > > Ok, we already had one i18n item on the todo-list. How about this > > [...] > Servlets often contains hard coded error strings. Replace these > with properties and redirect to an error.jsp where the error > message is shown. That's another scope and it can lead as well to the MVC framework to be used because there are different types of errors. If it's a validation error, generally the error page is the same as the validated page inviting the user to modify the wrong entry. This is tied to the MVC framework/validation system to be used. If it's a server error then it is generally a global error page. (Which for JSPs is generally set via the directive <%page errorPage="/errorPage.jsp" %> ) It can (and should) also be set globally via the web.xml (typically for a http 500 ), of course, in case both are defined the value in the jsp takes precedence. > > Don't hesitate to get started :) > > Which preferences do you mean specifically? (for example). I.e., which > problem is it solving? Admin preferences: Basically replace the hashtable that is serialized in a blob with use java.util.Preferences that you can query nicely. |