Ed wrote: > I am looking to create some generic modules (such as security > and user registration) that are shared by my applications. > Is it possible to package a self contained security module > which contains the login screen which can then pass control > to the main page of an application in a separate war file?
Wow, it's like our own little party. :) I wouldn't use a module for authentication/authorization (assuming you're talking about Struts Modules, used to be sub-applications I think). I have a standalone webapp that handles users setting up their accounts and it also handles authentication/authorization. If you make it a module, then it'll have to be part of *every* webapp. But if it's standalone, you can put a Filter in front of each of your other webapps and redirect the user off to log in if they haven't already. Then you don't have to worry about authentication over and over. If they can't authenticate, they simply never come back to the "main" webapp. It's the auth webapp's responsibility to deal with them. I suppose a module might make sense if this is a single webapp. But given the tendency of these things to grow and reproduce (I have 3 so far...) I'd really lean towards separating this reusable function into a separate webapp. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
