Subject: Re: [jade-develop] Odd serialization problem
From: John J. Mikucki (jjm7570@cs.rit.edu)
Date: Wed Jul 24 2002 - 14:55:31 MET DST
Thus spake Bellifemine Fabio (Fabio.Bellifemine@TILAB.COM):
> John, check that your class is not referenced by name, I mean: if you had a
> Class.forName() call, then it would be reasonable (and even correct) that
> your class is not serialized.
I'm not quite clear on what you mean by 'referenced by name'. I never call
Class.forName() in my code, so I can rule that interpretation out. My other
interpretation is that you're asking where my code contains the 'Tool' data
type. I only use the Tool data type in 2 places: the ToolBelt which stores
objects of subclasses of Tool (henceforth called Tools), and the actual NSBs
that use them. However, in the agent in question, no NSBs use Tools, and no
Tools are loaded.
Proceeding on the assumption that the JVM is unable to find the Tool class (as
referenced by the ToolBelt) when moving an agent, I am led to ask what could
remove elements from the JADE system's available class list. As all this is
taking place on the same JVM, launched in the same environment, I'd expect it
would work identically on any container. I'd imagine that it finds the Tool
class initially, as the agent happily loads into the container where I create
it. Where could the class have gone?
Thanks
John
-- Avoision, n: Avoidance, as practiced in 'Joisey.
This archive was generated by hypermail 2a22 : Wed Jul 24 2002 - 14:53:55 MET DST