Then don't call removeAttribute. Just call setAttribute to replace the
value of your key. Your app server's session implementation will (or
should) manage synchronization. Of course, one or two of your clients
might get a slightly stale list, but you can't help that. At least,
they'll never get a null pointer.
Alex Colic wrote:
>
> Oh,
>
> I thought about using removeAttribute() and then setting the attribute of
> the list again but I am worried about pulling a list out of the
> servletcontext just as a person might be accessing a page that needs that
> list.
>
> Regards
>
> Alex
