Get rid of modules. They aren't worth the hassle. You can easily split up your struts config without using modules.
On 9/28/07, Givler, Eric <[EMAIL PROTECTED]> wrote: > > Can anyone assist with this? > > -----Original Message----- > From: Givler, Eric [mailto:[EMAIL PROTECTED] > Sent: Saturday, September 22, 2007 1:25 AM > To: user@struts.apache.org > Subject: [s1.35] Need help with Struts and Modules > > > Hello, > > Let me just say that I'm struggling at times writing my first production > Struts application. The issue that I'm trying to wrestle with now is that > part of the application requires security, and part of it should allow > general access to the public. This sounds like a case for modules (I > think). So, I separated the code into a main folder, and then two other > folders (the secure, and another subsystem which is not secure). > > If I need to have the unprotected system and the protected system SHARE > some code as well, I'm assuming I have to keep that in the default module, > since otherwise, a security constraint would pop up when the unauthenticated > user tried to hit those pages. If I'm in the authenticated module and I > want to start a process that's defined in my default module, how would I do > that? > > That is, would it be as simple as adding a link to my JSP in my auth'd app > pointing back to the unauth'd: > <html:link module="" path="/StartApp.do" >Start an application > process</html:link> > > Now, I have two users running app entry (one auth'd and one not). If they > start an application and cancel it, they should return to their prospective > "subsystem". What am I setting up in my struts-config.xml file(s) to > handle this, and then in my action class? Can you be specific on this (with > an example of code)? > > I really appreciate any help on this one - Thanks much, > > Eric >
