It's not a secret anymore!
The moose likes Servlets and the fly likes Static Properties in Classes used by Servlets Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "Static Properties in Classes used by Servlets" Watch "Static Properties in Classes used by Servlets" New topic

Static Properties in Classes used by Servlets

Mike R.

Joined: Dec 26, 2003
Posts: 1
Assume I have a class X that has a static method that returns a static property of class X. Class X is used by various servlets in two web applications running under different contexts in the same servlet container.
My question is this - Within what scope is the static method guaranteed to return identical references to the static property of X? Is the property guaranteed to be static within a single web application or across all applications running in the servlet container? Is this at all dependent on the implementation of the servlet container or defined in the servlet specification somewhere?
Tim Baker
Ranch Hand

Joined: Oct 04, 2003
Posts: 541
As far as I know they are all shared within the same JRE. I can't think of any reason why a container would put different contexts in different JREs. I'm not sure what the JSP spec says about this.

Kim Jong II (North Korea's Dear Leader) said:Nuclear weapons don't kill people, people kill people.
Frank Carver

Joined: Jan 07, 1999
Posts: 6920
It's not so much the JRE that matters as the classloader context. Servlet containers are free to load different applications using separate classloaders, and often do. This means that static information in one application is often different from that in another application in the same container.
Why not try it in your container and let us know what happens?

Read about me at ~ Raspberry Alpha Omega ~ Frank's Punchbarrel Blog
Ken Robinson
Ranch Hand

Joined: Dec 23, 2003
Posts: 101
From this article, which basically says:
Here's a small change with a big impact: In API 2.3, a servlet container (a.k.a. the server) will ensure that classes in a Web application not be allowed to see the server's implementation classes. In other words, the class loaders should be kept separate.

it appears that it would indeed be seperate. Of course, verifying this in your container as suggested by Frank Carver above is always a great idea.
I agree. Here's the link:
subject: Static Properties in Classes used by Servlets
It's not a secret anymore!