On Sat, 14 Aug 1999, hhito wrote:
[ ... ]
> This gives other servlets access to the same services simply by
> calling MyServlet.performService(). This saves me from messing with
> getServlet(). Are there any syncronization issues invloved here or
> any other problems I'm not aware of?
I can't offhand think of any problems this would cause. However, I
also can't see why you'd want to do it this way, from an
object-oriented design perspective. If the method is static, that
means it doesn't really have anything to do with the specifics of that
servlet per se, in which case it seems to me its job should be done by
a non-servlet class. Think of your servlet(s) as the interface
between the web and your application; you'd want to keep the
application code as much out of the servlets as possible, and that
would be the place for the functionality contained in that static
method.
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
