Merten Schumann wrote:
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
java.lang.IllegalStateException: XMLList
I worked to re-implement E4X support for the 1.6R7 release, removing the
dependency on XMLBeans.
When I was working on this, I had trouble managing the state for the
LazilyLoadedCtor stuff; I believe I ended up having to use some sort of
hack in the end. If no one has been in there recently, it's quite
possible that there was some sort of precondition or set of possible
conditions I didn't anticipate. That said, I have at least two
suggestions of test cases that (in my dim recollection) might shed some
light.
(1) Do you have Apache XMLBeans in the classpath available to Rhino?
If so, take it out and see what happens.
(2) Have you set the JavaScript version variable to something less than
1.6? If so, Rhino would try to disable E4X, which may be a condition I
didn't test.
-- David P. Caldwell
http://www.inonit.com/
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
