Mailing-List: contact user-help@guacamole.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@guacamole.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGPRPhe6Dbd-3ec7AbYmvq0aOiWP1bf2YOkFMs_9iJ98pG8FmQ@mail.gmail.com>
References: <CAGPRPhfzLjo-QryVn=C6UKJXgFOFBb7Qrx7F0ySUOtGLj+dpvQ@mail.gmail.com>
 <CALKeL-PsNOhXVxDpnXh=hYOOD7oa6e_WJV-iESLy18Zaxf2nbQ@mail.gmail.com>
 <CAGPRPhcGqeNzy-peU5yqbo=Djnm2JrOcmzcxFuAg-sH1Dfzd3Q@mail.gmail.com>
 <CAFjj603-UAFZ3pi6S7gUHZxDJzB7Vx2uShC38HCSyKBVGFy4Vg@mail.gmail.com>
 <CAGPRPheqcf3t5aKETwNsjo6G_u05DvaekpA_zqB+jhX7EsM8ng@mail.gmail.com> <CAGPRPhe6Dbd-3ec7AbYmvq0aOiWP1bf2YOkFMs_9iJ98pG8FmQ@mail.gmail.com>
From: Mike Jumper <mike.jumper@guac-dev.org>
Date: Mon, 4 Dec 2017 23:17:26 -0800
Message-ID: <CALKeL-MZ9vjr14fzAQKyErPS-=R2kxgT87DNBrZqHLVKa2+Xrw@mail.gmail.com>
Subject: Re: Authentication issue after build client war file
To: user@guacamole.apache.org
Content-Type: multipart/alternative; boundary="089e0828d86ce9ffc0055f92a27a"
archived-at: Tue, 05 Dec 2017 07:18:13 -0000

--089e0828d86ce9ffc0055f92a27a
Content-Type: text/plain; charset="UTF-8"

On Mon, Dec 4, 2017 at 7:48 AM, David Rodriguez <djrm05@gmail.com> wrote:

> Hi there,
>
> Any clue why I still unable to see the Spanish keyboard layout after
> follow the steps mentioned before?
>
>
The contents of the keyboard layout field within the connection parameters
in the admin UI are determined by the "rdp.json" file which you edited.
Assuming that the edit was correct (you didn't accidentally produce invalid
JSON), that should be all you need for the choice to be made available. You
don't even technically need to add the translation - it will appear as a
huge uppercase machine-readable string, but will still be a choice.

If the choice is not available at all, then the only possibility is that
the version of Guacamole deployed was not built against the guacamole-ext
that you modified. This could be because:

1) Tomcat did not actually redeploy Guacamole when you copied the new
guacamole.war over (you may need to clear the working directory containing
the exploded contents of the .war and restart Tomcat to force Tomcat to
re-extract and redeploy)
2) You did not copy the new guacamole.war over
3) The "guacamole" project within guacamole-client was not rebuilt against
the "guacamole-ext" containing your modifications

If nothing is working in your attempts to resolve this, I would suggest:

1) Doing a full "mvn clean install" from the root of the "guacamole-client"
source directory. This will rebuild absolutely everything, and will ensure
guacamole is built against your modified guacamole-ext.
2) Stop Tomcat
3) Remove the existing guacamole.war and associated guacamole/ directory
(automatically created by Tomcat upon deployment)
4) Copy guacamole/target/guacamole*.war in place
5) Start Tomcat
6) Verify that Tomcat automatically extracted the .war

At that point, assuming your changes are indeed present on the source tree
you built, the choice should now be available.

Looking back at GUACAMOLE-233, though ... this shouldn't be necessary. The
keymap was added at the guacamole-server level, and should also have been
added to guacamole-client. I've reopened the issue in JIRA, as this was
definitely an oversight.

- Mike

--089e0828d86ce9ffc0055f92a27a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Dec 4, 2017 at 7:48 AM, David Rodriguez <span dir=3D"ltr">&lt;<a href=
=3D"mailto:djrm05@gmail.com" target=3D"_blank">djrm05@gmail.com</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi there,<div=
><br></div><div>Any clue why I still unable to see the Spanish keyboard lay=
out after follow the steps mentioned before?</div><div><br></div></div></bl=
ockquote><div><br></div><div>The contents of the keyboard layout field with=
in the connection parameters in the admin UI are determined by the &quot;rd=
p.json&quot; file which you edited. Assuming that the edit was correct (you=
 didn&#39;t accidentally produce invalid JSON), that should be all you need=
 for the choice to be made available. You don&#39;t even technically need t=
o add the translation - it will appear as a huge uppercase machine-readable=
 string, but will still be a choice.</div><div><br></div><div>If the choice=
 is not available at all, then the only possibility is that the version of =
Guacamole deployed was not built against the guacamole-ext that you modifie=
d. This could be because:<br><br></div><div>1) Tomcat did not actually rede=
ploy Guacamole when you copied the new guacamole.war over (you may need to =
clear the working directory containing the exploded contents of the .war an=
d restart Tomcat to force Tomcat to re-extract and redeploy)</div><div>2) Y=
ou did not copy the new guacamole.war over</div><div>3) The &quot;guacamole=
&quot; project within guacamole-client was not rebuilt against the &quot;gu=
acamole-ext&quot; containing your modifications</div><div><br></div><div>If=
 nothing is working in your attempts to resolve this, I would suggest:</div=
><div><br></div><div>1) Doing a full &quot;mvn clean install&quot; from the=
 root of the &quot;guacamole-client&quot; source directory. This will rebui=
ld absolutely everything, and will ensure guacamole is built against your m=
odified guacamole-ext.</div><div>2) Stop Tomcat</div><div>3) Remove the exi=
sting guacamole.war and associated guacamole/ directory (automatically crea=
ted by Tomcat upon deployment)</div><div>4) Copy guacamole/target/guacamole=
*.war in place</div><div>5) Start Tomcat</div><div>6) Verify that Tomcat au=
tomatically extracted the .war</div><div><br></div><div>At that point, assu=
ming your changes are indeed present on the source tree you built, the choi=
ce should now be available.</div><div><br></div><div>Looking back at GUACAM=
OLE-233, though ... this shouldn&#39;t be necessary. The keymap was added a=
t the guacamole-server level, and should also have been added to guacamole-=
client. I&#39;ve reopened the issue in JIRA, as this was definitely an over=
sight.</div><div><br></div><div>- Mike</div><div><br></div></div></div></di=
v>

--089e0828d86ce9ffc0055f92a27a--