On 2008.05.13., at 18:08, helge wrote: > Hm, not sure what to do now. Should NativeString() be a public class?
Not really. Just creating the Java object instance that's backing the native JS string is not enough, as it needs to be connected to its prototype object etc. Therefore, there's little point in exposing it in the Java API. If you want to create a NativeString programmatically, you'd use: Context.newObject(scope, "String", constructorArgs); You need a scope, so the Context can locate the JS constructor named "String" and invoke it, and you can also pass arguments to the constructor. Attila. _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
