Hi all,
I've a web application that uses Oscar for plugin management and Wicket
for generating the GUI. On our development list we have a problem with
how to serialize and deserialize objects coming from within Oscar
bundles. This is necessary when running a Wicket application on a
cluster, or when the httpsession is stored on disk or in a database.
Our main concern is that the application server does not know about the
objects loaded through Oscar, as Oscar uses its own classloader. So
serialization will happen, but when deserialization kicks in, the
application server's classloader will instantiate the object, and the
object will live outside the Oscar bundle, and not be connected in any
way to Oscar.
For business objects, this may not be a big problem (can be solved by
not storing the object itself, but an ID of sorts to resolve the object
after deserialization), but for packaged resources in the bundle, for
instance markup, javascript, images, it can be.
Do you have any ideas on how to tackle this problem?
With regards,
Martijn Dashorst
