I've tried to start over from scratch, but if I mirror the process listed, I get this:
Extension "xyz.jar" could not be loaded: Unable to read extension: xyz.jar but this was produced via zip -r xyz.jar * in the theme directory. I'm copy/pasting this on a windows box into putty, are there some characters that might be a problem?? On Mon, Sep 18, 2017 at 3:39 PM, dan <[email protected]> wrote: > it does indeed remove the error, and gives a new one: > ERROR o.a.g.extension.ExtensionModule - Extension "xyz.jar" could not be > loaded: guac-manifest.json is not valid JSON: xyz.jar > > > On Mon, Sep 18, 2017 at 3:35 PM, Mike Jumper <[email protected]> > wrote: > >> On Mon, Sep 18, 2017 at 1:40 PM, dan <[email protected]> wrote: >> >>> Here are the lines for loading extensions: >>> 20:37:35.278 [localhost-startStop-1] INFO o.a.g.extension.ExtensionModule >>> - Extension "MySQL Authentication" loaded. >>> 20:37:35.283 [localhost-startStop-1] ERROR o.a.g.e.LanguageResourceService >>> - Unable to merge language resource "en": Unexpected character ('}' (code >>> 125)): was expecting double-quote to start field name >>> at [Source: sun.net.www.protocol.jar.JarUR >>> LConnection$JarURLInputStream@2af5f30a; line: 4, column: 10] >>> 20:37:35.283 [localhost-startStop-1] INFO o.a.g.extension.ExtensionModule >>> - Extension "xyz" loaded. >>> >>> No theming extension and a syntax error that I'm assuming is related to >>> the lack of theming?? >>> >>> >> The string "Theming Extension" referred to by Erik is actually the name >> of the extension as declared in guac-manifest.json. That much looks correct >> here, as your extension is listed by name as loaded. >> >> The error regarding the failure to merge the language resource refers to >> your translation JSON, and is preventing your extension from loading fully. >> Looking at what you posted previously: >> >> { >> "APP" : { >> "NAME" : "XYZ APP", >> } >> } >> >> You have a trailing trailing comma after "XYZ APP", which JSON does not >> allow. If you remove that comma, rebuild your extension, and restart >> Tomcat, I expect that error will disappear. >> >> - Mike >> >> >
