W
wgblackmon
My team is enhancing and maintaining a very large and in some places
very old (8 yrs.) (pre-.jsp, servlets etc.) web app. As you can
imagine, there is no coherent strategy for error handling and error
stack traces are frequently throw onto the screen for the user to see.
There is also no coherent strategy for defining text in the .jsp pages
and the pages that are generated by the older portions of the
application. Struts is out of the question as is Spring. We need to
find a way to:
1. Define and maintain specific error messages in a central location
that can be maintained in multiple languages.
2. Do the same for text messages that are displayed in .jsp pages.
I've looked into using ResourceBundles in properties files. Has anyone
out there successfully used ResourceBundles for error messages and
displayed text? The application will eventually have be upgraded to a
Spanish version so we need to get a handle on this ASAP.
All suggestions are greatly appreciated!
very old (8 yrs.) (pre-.jsp, servlets etc.) web app. As you can
imagine, there is no coherent strategy for error handling and error
stack traces are frequently throw onto the screen for the user to see.
There is also no coherent strategy for defining text in the .jsp pages
and the pages that are generated by the older portions of the
application. Struts is out of the question as is Spring. We need to
find a way to:
1. Define and maintain specific error messages in a central location
that can be maintained in multiple languages.
2. Do the same for text messages that are displayed in .jsp pages.
I've looked into using ResourceBundles in properties files. Has anyone
out there successfully used ResourceBundles for error messages and
displayed text? The application will eventually have be upgraded to a
Spanish version so we need to get a handle on this ASAP.
All suggestions are greatly appreciated!