Hi Tonny,
Thanks for the info. I am including js.jar so I don't think that's the problem.
Here's the complete exception:
java.lang.Exception: Unknown language: text/ecmascript
at
org.apache.batik.bridge.BridgeContext.getInterpreter(BridgeContext.java:575)
at
org.apache.batik.bridge.BaseScriptingEnvironment.getInterpreter(BaseScriptingEnvironment.java:320)
at
org.apache.batik.bridge.BaseScriptingEnvironment.getInterpreter(BaseScriptingEnvironment.java:316)
at
org.apache.batik.bridge.BaseScriptingEnvironment.dispatchSVGLoad(BaseScriptingEnvironment.java:639)
at
org.apache.batik.bridge.BaseScriptingEnvironment.dispatchSVGLoad(BaseScriptingEnvironment.java:612)
at
org.apache.batik.bridge.BaseScriptingEnvironment.dispatchSVGLoadEvent(BaseScriptingEnvironment.java:599)
at
org.apache.batik.bridge.UpdateManager.dispatchSVGLoadEvent(UpdateManager.java:239)
at
org.apache.batik.bridge.UpdateManager.dispatchSVGLoadEvent(UpdateManager.java:220)
at
org.apache.batik.swing.svg.SVGLoadEventDispatcher.run(SVGLoadEventDispatcher.java:100)
I see that InterpreterPool has a method putInterpreterFactory() but according
to NetBeans "Find Usages" it's never being called in the source the way I have
it set up.
Where is it supposed to be called from?
Thanks,
-JCT
> -----Original Message-----
> From: Tonny Kohar [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 18 September 2008 22:36
> To: [email protected]
> Subject: Re: Batik 1.8 unknown language error
>
> Hi,
>
> On Thu, Sep 18, 2008 at 6:02 PM, John C. Turnbull
> <[EMAIL PROTECTED]> wrote:
> > When I build Batik 1.8pre from the latest sources, I get an error
> when I run
> > Squiggle complaining "Unknown language: text/ecmascript" whenever I
> open an
> > SVG that uses JavaScript.
> >
> > Clearly I have done something wrong or missed something... but what
> > exactly? What is it that binds Batik to JavaScript that I am
> obviously not
> > doing?
>
> Not sure what you are doing given the context. But make sure to
> include js.jar (this is the mozilla rhino interpreter).
> Also for Javascript to work correctly, the DOM document should have
> document URI (either fake or real, but can't be null). That kind of
> error is usually (not always) because you create document on the fly
> but forget to set the document URI
>
> We have the similar error in our case last time, but it is due to we
> are incorrectly clone the document and forget to set the document URI.
>
> Cheers
> Tonny Kohar
> --
> Sketsa SVG Editor
> imagine, design, create ...
> http://www.kiyut.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: batik-users-
> [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
