Re: James / Excalibur ThreadPool conflict
Stephen McConnell <[email protected]> Sun, 12 Jan 2003 01:15:06 +0100
| Newsgroups | gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel |
|---|---|
| Message-ID | <[email protected]> |
Peter Donald wrote: >On Sun, 12 Jan 2003 10:43, Peter M. Goldstein wrote: > > >>A method was removed from the org.apache.avalon.excalibur.thread.ThreadPool >>interface. Specifically, the execute(Runnable) method. As I said above, >>considering the interface was already deprecated I don't understand why >>this method was removed. Seems to violate the whole point of deprecating >>interfaces. >> >> > >You will notice that org.apache.avalon.excalibur.thread.ThreadPool extends >org.apache.excalibur.thread.ThreadPool and >org.apache.excalibur.thread.ThreadPool has the execute(Runnable) method and >thus any instance of org.apache.avalon.excalibur.thread.ThreadPool also has >the execute(Runnable) method via inheritance. > > > >>Everything does work if you compile/run/etc. against the old jar. >> >> > >Everything will work if you compile against old jar and run with new jar. >Everything will work if you compile against old jar and run with old jar. >Everything will work if you compile against new jar and run with new jar. > >What will not work is compiling against the new jar and running against the >old jar. This is the problem. > How do explain a NoSuchMethodException when running against the new jar ? Steve. -- Stephen J. McConnell mailto:[email protected] http://www.osm.net