Hi Kenji,
Kenji Konaka wrote:
>
>...does the(j2ee) specs say anything about life-cycle of a
>classloader(s) used for an j2ee app? (eg.,a classloader will
>continue to live as long as the app is deployed) or each
>containers are just free to implement its own schemes?
>
No, the spec doesn't mandate anything - it's up to the application
server implementation (a "quality of implementation feature"). With J2EE
app servers there is typically one ClassLoader per container (or
archive) even with multiple containers per Server VM. Decent
application servers should remove all references to a container (or
archive's) ClassLoader when the container is removed from the server.
How this is done is vendor specific since server/container management
is outside the scope of the spec.
What you can rely on is the fact that the classes & resources loaded to
support J2EE modules running in one container should never be visible to
different J2EE modules running in another container in the same VM.
What you will also find is that several Servlet/JSP implementations
(such as Tomcat) have the ability to reload JSP/Servlet class files from
disk if the class has changed between client invocations in order to
allow web developers to quickly test changes to their web components.
However, such behaviour is configurable and is usually disabled for
production systems as it imposes a signigicant performance hit.
j.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
