Thanks for the information. That was it, I put the serialized class in
its own jar stuck it in the class path and all was well.
On Jan 13, 2009, at 3:16 PM, Dustin wrote:
On Jan 13, 1:30 pm, Macster2007 <[email protected]> wrote:
Hmnn.. Right now I am testing the put and get from the same process.
That means it should successfully archive/unarchive correctly right?
The process isn't really relevant.
I like to think of java as an operating system. Within it there can
be numerous classloaders (which are about half of what you'd think of
as processes in the sense that they provide access to stuff).
Classloaders may exist within the context of other classloaders in
such a way that forms a sort of hierarchy. Things down the hierarchy
can load classes from up the hierarchy (e.g. java.lang.String), but
things up the hierarchy can't load classes from further down (e.g. a
class from within your web app).
