Easy - the controller servlet is the ONLY servlet in the application. It
calls "action classes" to carry out tasks, but there are not servlets. They
are "servlet aware" in that they accept servlet artifacts in their execute()
method as parameters, so they can access parameters, etc. But to answer your
question, some of the beauty of this is that the controller is the only
servlet, hence all security, session checking, etc happens there.
Bill Hines
Hershey Foods
-----Original Message-----
From: Marc Krisjanous [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 07, 2000 7:52 AM
To: [EMAIL PROTECTED]
Subject: Servlet Controller - stopping other Servlets calling action
Servl ets
Hi all,
I have seen some discussions on the Servlet Controller concept here and I
would like to know how you can stop other Servlets or users for that matter,
calling other Servlets that are only allowed to be called by the Servlet
Controller.
Best Regards
Marc
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
