Re: Another question about codebases and jar versions

> No a new class loader will be created for that annotation, meaning
> that classes defined in that new loader are not equal to those in
> the class loader associated with the old URL. I hope this helps in
> redefining your questions.

Great. That was nagging me as I wrote it, but I thought, no, there
were times when one would end up with the same class loader.

> In general this is the behavior you want.

Yes, that helps with the questions I had. As in several go away.

> There is however a use case where this is nasty.

Dagnabbit.

> In this case I would want to be able to sent an old codebase
> annotation to the client, which might result in them not getting the
> bug-fix but if the bug is not hindering them at least it would help
> them to continue.

Is there a typical way to do this? 

Or is there a conventional way to get a client with old objects to
fail and take some app-specific upgrade measures?

Or?

Thanks
-Patrick

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]