src/java.corba/share/classes/com/sun/corba/se/spi/extension/ServantCachingPolicy.java

*** 42,52 ****
  * If servant caching is used, there are two different additional
  * features of the POA that are expensive:
  * <ol>
  * <li>POA current semantics
  * <li>Proper handling of POA destroy.
! * <ol>
  * POA current semantics requires maintaining a ThreadLocal stack of
  * invocation information that is always available for POACurrent operations.
  * Maintaining this stack is expensive on the timescale of optimized co-located
  * calls, so the option is provided to turn it off.  Similarly, causing
  * POA.destroy() calls to wait for all active calls in the POA to complete
--- 42,52 ----
  * If servant caching is used, there are two different additional
  * features of the POA that are expensive:
  * <ol>
  * <li>POA current semantics
  * <li>Proper handling of POA destroy.
! * </ol>
  * POA current semantics requires maintaining a ThreadLocal stack of
  * invocation information that is always available for POACurrent operations.
  * Maintaining this stack is expensive on the timescale of optimized co-located
  * calls, so the option is provided to turn it off.  Similarly, causing
  * POA.destroy() calls to wait for all active calls in the POA to complete