Subj : Re: Rhino: ScriptableInputStream/ScriptableOutputStream enhancements
To   : Attila Szegedi
From : Igor Bukanov
Date : Sun Sep 12 2004 03:00 am

Attila Szegedi wrote:
> Hi folks,
> 
> I'm trying to use ScriptableInputStream/ScriptableOutputStream for  
> serializing/deserializing JavaScript scopes, and I have two problems 
> with  them:
> 
> 1. ScriptableOutputStream will trigger evaluation of all 
> LazilyLoadedCtor  objects in excludeStandardObjectNames(). This is 
> especially problematic in  case of serializing against a shared scope 
> that is already sealed.
> 
> 2. lookupQualifiedName uses Scriptable.get instead of  
> ScriptableObject.getProperty, therefore if the excluded objects are  
> dispersed among several shared scopes, each being the other's  
> parent/prototype, it's not possible to exclude them all, since the  
> excluded objects must all be immediate (not parent or prototype)  
> properties of the scope passed in the stream constructor.
> 
> 3. It'd be rather helpful if ScriptableInputStream overrode  
> ObjectInputStream.resolveClass() to use  
> Context.getCurrentContext().getApplicationClassLoader() to resolve the  
> classes.
> 
> If you folks find any of these to be valid concerns, I can raise them 
> as  Bugzilla issues (and even contribute patches immediately).

Yes, the concerns are valid are patches would be nice!

Regards, Igor

.