This is how I'm envisioning my application flow. Is this standard, completely out of whack, or somewhere in between?
1. User enters/clicks on context URL, like /track. 2. Appserver finds welcome file, index.jsp. 3. index.jsp does a forward, via global-forward w/ redirect, to /track/do/login. 4. login action sees username is blank and forwards to /track/login.jsp. (Can't hide jsp in WEB-INF because we are using WebLogic 6.1) 5. User enters username and password, and submits to /track/do/login. 6. login action sees username is NON blank, calls login class and upon login success, forwards w/ redirect to /track/do/track. 7. track action detects form is empty and forwards to /track/track.jsp. 8. User enters data and submits to /track/do/track 9. track form performs validation. 10. track action submits user data to track business class. 11. Business class returns result object. 12. track action puts result object in response/session. 13. track action forwards to /track/results.jsp. 14. results.jsp extracts result object from response/session and displays to user. I've also got a LoginFilter which checks that the user is logged in before allowing access to /do/track, but I didn't want to complicate the outline. Also, what is the purpose of the input attribute of an action? Thanks. Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
