On Mon, 20 Aug 2001, [iso-8859-1] Andrés Aguiar wrote:
> Now, in the servlet spec says:
>
> 'Although a Container Provider implementation of a class reloading scheme
> for ease of development is not required, any such implementation must ensure
> that all servlets, and classes that they may use, are loaded in the scope of
> a single class loader. This requirement is needed to guarantee that the
> application will behave as expected by the Developer.
>
> As a development aid, containers are encouraged to maintain the full
> semantics of notification to session binding listeners if they
> determine to terminate sessions in order to reload classes.
>
> Previous generations of containers created new class loaders to load a
> servlet, distinct from class loaders used to load other servlets or classes
> used in the servlet context. This could cause object references within a
> servlet context to point at unexpected classes or objects, and cause
> unexpected behavior.'
>
> I'm not sure if this paragraph is referring to the case I'm describing, but
> if not, it seems pretty close...
my two bob - from a non-tc developer... in tc3.x I think you can cause a
ClassCastException by recompiling the entire web-inf/classes dir - this is
because servlets will be reloaded but beans wont. the above paragraphs I
think state that its an all or nothing and everything must be reloaded, or
nothing at all. that said, what you've described makes sense to me, and
seems to conform to the spec.
again - my 2c
cheesr
dim
