Hello Bediako, no, I don't use E4X - but thanx anyway.
What I'm doing, I'm playing around with setting parent and prototype, defining some properties like this ScriptableObject.defineProperty(root_scope, "$$Args", null, ScriptableObject.PERMANENT | ScriptableObject.READONLY); and then I try to seal the ScriptableObject(). cu Merten From: Bediako George [mailto:[email protected]] Sent: Friday, July 10, 2009 3:31 PM To: Merten Schumann Cc: [email protected] Subject: Re: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList Hullo Merten, I don't have an answer to your problem, but I do have a small clue. I believe XMLList is used by E4x which 1.6 supports. Are you using E4x in your code? Perhaps there was a change of some sort in how E4X is implemented in 1.7 versus 1.6? Regards, Bediako On Fri, Jul 10, 2009 at 9:26 AM, Merten Schumann <[email protected]<mailto:[email protected]>> wrote: Hello, I've got an application using Rhino 1.6R1 - there was no need to update it, no problems. :-) Now I tried to make the step to 1.7R2. My application compiles, so I'm not using any functionality which is gone for some reason - if there's such a difference between 1.6R2 and 1.7R2 at all. But when I run the application, I end up with java.lang.IllegalStateException: XMLList at org.mozilla.javascript.LazilyLoadedCtor.getValue(LazilyLoadedCtor.java:101) at org.mozilla.javascript.ScriptableObject.getImpl(ScriptableObject.java:2034) at org.mozilla.javascript.ScriptableObject.get(ScriptableObject.java:287) at org.mozilla.javascript.IdScriptableObject.get(IdScriptableObject.java:387) at org.mozilla.javascript.LazilyLoadedCtor.buildValue(LazilyLoadedCtor.java:118) at org.mozilla.javascript.LazilyLoadedCtor.init(LazilyLoadedCtor.java:89) at org.mozilla.javascript.ScriptableObject.sealObject(ScriptableObject.java:1567) at [my class] Anyone else experiencing such a problem? I was searching for IllegalStateException and XMLList - but seems there's no issue like this out there. XMLList is a class within Rhino itself. I think I read here in the past about changes to ScriptableObject.sealObject() - in terms of Context.enter/exit - not sure about it. There was a fix for a problem with Rhino loading it's own properties lazy - suggested by wolffiex - I tried it, but it's not helping me out here (should it?) I'll debug my code and step into Rhino code next. I do not use this XMLList class from my code - so I don't feal guilty ;-) If I cannot fix my problem, I'll try to write a test case to demonstrate the problem. Thanx Merten _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected]<mailto:[email protected]> https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino -- Bediako George Partner - Lucid Technics, LLC Think Clearly, Think Lucid (p) 202.683.7486 (f) 703.563.6279 _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
