Re: Storing JSP content in a Database
Monday, May 20, 2002 06:23 AM
Ouch, sounds painful. Here's what I would do in that situation. Store in the database the action key to take. Then on the jsp page, that action key triggers a specfiic jsp tag. You could even put that in a JSP include and pass the action tag to the JSP.
The scenario you are describing violates the MVC concept in that the View is completely dependent on the model and you will decrase significantly the maintainability of the app.
Okay, what are you talking about? :) Persistant data should typically involve data that is revelant for many years to come. Will this application still be using custom JSP tags in years to come?