Andy, Depending on the complexity of the application, you may want to consider having the user call an action first, not a jsp. The action can do any setup for the jsp page, such as retrieving any collections you may need to populate dropdown lists in the page. Even if the action does nothing right now, if wanted to add that type of functionality later or other functionality that would require an action beforehand, the users would not need to change their bookmarks.
-Rob -----Original Message----- From: Andy Engle [mailto:[EMAIL PROTECTED] Sent: Friday, February 13, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: Calling JSPs directly Hi all, I'm working with a web application in which I have multiple pages of information, currently located in PHP files. I want to convert these PHP files into JSPs, and then make them available to be directly called within my web application. I would like to have these JSPs available for direct access because I want to make it easy for users of this application to bookmarks whatever pages they're interested in going back to from time to time. Each page will have a form, which will be submitted to a Struts action when submitted, and then from there I want the action to update the database, then return the same, updated JSP to the user. I'm wondering if making JSPs available to the user in this manner is a poor practice, and if so, what would be a better way of doing it? Furthermore, will I run into any problems with the Struts custom tags or tiles by taking this approach? Thanks very much for sharing your thoughts. Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
