|1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList||Merten Schumann||7/10/09 6:26 AM|
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.
But when I run the application, I end up with
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'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 ;-)
|Re: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList||Bediako George||7/10/09 6:30 AM|
I don't have an answer to your problem, but I do have a small clue. I
On Fri, Jul 10, 2009 at 9:26 AM, Merten Schumann <Merten....@asg.com>wrote:
|RE: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList||Merten Schumann||7/12/09 11:41 PM|
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().
From: Bediako George [mailto:bediako...@lucidtechnics.com]
Sent: Friday, July 10, 2009 3:31 PM
To: Merten Schumann
Subject: Re: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList
|Re: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList||David P. Caldwell||7/13/09 10:50 AM|
Merten Schumann wrote:
> But when I run the application, I end up with
I worked to re-implement E4X support for the 1.6R7 release, removing the
When I was working on this, I had trouble managing the state for the
(1) Do you have Apache XMLBeans in the classpath available to Rhino?
-- David P. Caldwell
|Re: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList||rehzon||4/6/10 5:11 AM|
I was getting the same problem but it went away when i removed xalan.jar and xercesImpl.jar from the classpath (im using jdk 1.6)
|RE: 1.7R2 instead of 1.6R1, sealing an object leads to IllegalStateException: XMLList||Merten Schumann||4/6/10 5:26 AM|
kind of "glad" someone else xperienced this problem ;-)
For some reasons, I had to keep Apache Xerces in my classpath in the past - now this issue is resolved for me too, even JDK 1.5 is enough for my XML usage