Knut Wannheden wrote:
David,
I think this might be a bug. Could you provide a complete test case
exposing this behaviour?
Sorry - not really - i's my customers code :-)
Shouldn't be any need for it either.
But, it's something like this:
My runnable object ("class Runner"):
....
void run(){
try {
//a series of this:
MyService service = Registry.getService(MyService.class);
//use service
log(service); //implicit call of toString()
}
And the main-class:
EDU.oswego.cs.dl.util.concurrent.PooledExecutor pool = new
PooledExecutor(60);
Stack users;
while (!users.isEmpty){
pool.execute( new Runner(users.pop()) );
}
All the service-interfaces I use extend a common interface.
All the implementing classes of these interfaces extend a common
abstract class (implementing the common interface - and leaving some
methods as abstracts to be implemented by the end-class.)
And - importantly - the toString() is declared in the common interface -
and implemented by the abstract common class. This might be the problem???
I'll build to versions for the next test - one with the toString() in
the common interface - and one with toString() left out - and see if it
disappears.
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
