Hello, just in the final countdown regarding the IBM-157 test. I have two questions that i would like to discuss with you. The first one is about the distributable flag within the web.xml deployment descriptor. Is there a more detailed description when we can set this flag to distributable as in the servlet spec? There are all these best practices like implementing the serializable interface, don't use member variables in servlets, don't use the SingleThreadModel, no large object graphs in the session and so on, but is there a definition when a webapp is distributable and behaves the web container differently??
My second question is how looks the stack trace different when using a java exception breakpoint or a method entry breakpoint (caught / uncaught) ? -> question from ICE ... . Thanks for your answers.
With kind regards from Germany Gerd Watmann SCJP & OOA /OOD ;-)
posted 14 years ago
Originally posted by Gerd Watmann:
... The first one is about the distributable flag within the web.xml deployment descriptor. Is there a more detailed description when we can set this flag to distributable as in the servlet spec?
distributable is new with Servlet 2.2 api. Below is from developer.java.sun.com
What's New in Java Servlet API 2.2? By Jason Hunter; Reprinted from JavaWorld October 1999
Distributed Applications A few clarifications were also made in 2.2 with regards to distributed applications, in which application components can be spread across multiple back-end server machines. The specification dictates that, for an application marked as distributable in its deployment descriptor, there will be a single ServletContext instance per JVM. This means the context attributes cannot be used to share global information. Global information in a distributed app needs to be stored externally from the Web server, as is the case in database or EJB component.
You have to be odd to be #1 - Seuss. An odd little ad:
the new thread boost feature brings a LOT of attention to your favorite threads