Přeskočit na hlavní obsah

A všichni si rozumíme 2 - klávesové zkratky

Psali jste někdy lokalizované aplikace ve Swingu? A jak jste řešili klávesové zkratky (Mnemonics) pro různé jazyky? Já jsem se při programování JSignPdf rozhodl použít přístup, který znám z Delphi. V resource řetězcích vložím ampersand (&) před písmeno, které má být použito jako klávesová zkratka. Když chci zobrazit znak ampersand, tak napíšu dva za sebe.

A jak to funguje v kódu? Mám wrapper pro ResourceBundle, který nabízí mimo metod pro přístup k lokalizovaným stringům i metodu, která vrací MnemonicIndex (pozici znaku, který je použit jako klávesová zkratka).

* Returns message for given key from active ResourceBundle
* @param aKey name of key in resource bundle
* @return message for given key
public String get(final String aKey) {
  String tmpMessage = bundle.getString(aKey);
  if (tmpMessage == null) {
    tmpMessage = aKey;
  } else {
    tmpMessage = tmpMessage.replaceAll("&([^&])", "$1");
  return tmpMessage;

* Returns index of character which should be used as a mnemonic.
* It returns -1 if such an character doesn't exist.
* @param aKey resource key
* @return index (position) of character in translated message
public int getMnemonicIndex(final String aKey) {
  String tmpMessage = bundle.getString(aKey);
  int tmpResult = -1;
  if (tmpMessage != null) {
    int searchFrom = 0;
    int tmpDoubles = 0;
    int tmpPos;
    final int tmpLen = tmpMessage.length();
    do {
      tmpPos = tmpMessage.indexOf('&', searchFrom);
      if (tmpPos == tmpLen-1) tmpPos = -1;
      if (tmpPos>-1) {
        if (tmpMessage.charAt(tmpPos+1) != '&') {
          tmpResult = tmpPos - tmpDoubles;
        } else {
          searchFrom = tmpPos + 2;
    } while (tmpPos!=-1 && tmpResult==-1 && searchFrom<tmpLen);
  return tmpResult;

* Returns message for given key from active ResourceBundle and replaces
* parameters with values given in array.
* @param aKey key in resource bundle
* @param anArgs array of parameters to replace in message
* @return message for given key with given arguments
public String get(String aKey, String anArgs[]) {
  String tmpMessage = get(aKey);
  if (aKey==tmpMessage || anArgs == null || anArgs.length == 0) {
    return tmpMessage;
  final MessageFormat tmpFormat = new MessageFormat(tmpMessage);
  return tmpFormat.format(anArgs);

použití uvedeného wrapperu potom vypadá následovně (res je jméno instance wrapperu):

* Application translations.
private void translateLabels() {
  setTitle(res.get("gui.title", new String[] {Constants.VERSION}));
  setLabelAndMnemonic(lblKeystoreType, "gui.keystoreType.label");
  setLabelAndMnemonic(chkbAdvanced, "gui.advancedView.checkbox");

* Sets translations and mnemonics for labels and different kind of buttons
* @param aComponent component in which should be label set
* @param aKey message key
private void setLabelAndMnemonic(final JComponent aComponent, final String aKey) {
  final String tmpLabelText = res.get(aKey);
  final int tmpMnemIndex = res.getMnemonicIndex(aKey);
  if (aComponent instanceof JLabel) {
    final JLabel tmpLabel = (JLabel) aComponent;
    if (tmpMnemIndex>-1) {
  } else if (aComponent instanceof AbstractButton) {
    //handles Buttons, Checkboxes and Radiobuttons
    final AbstractButton tmpBtn = (AbstractButton) aComponent;
    if (tmpMnemIndex>-1) {
  } else {
    throw new IllegalArgumentException();

Resource fajl potom obsahuje takovéto záznamy:

gui.advancedView.checkbox=A&dvanced view
gui.alias.label=Key &alias


Populární příspěvky z tohoto blogu

Three ways to redirect HTTP requests to HTTPs in WildFly and JBoss EAP

WildFly application server (and JBoss EAP) supports several simple ways how to redirect the communication from plain HTTP to TLS protected HTTPs. This article presents 3 ways. Two are on the application level and the last one is on the server level valid for requests to all deployments. 1. Request confidentiality in the deployment descriptor The first way is based on the Servlet specification. You need to specify which URLs should be protected in the web.xml deployment descriptor. It's the same approach as the one used for specifying which URLs require authentication/authorization. Just instead of requesting an assigned role, you request a transport-guarantee . Sample content of the WEB-INF/web.xml <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" version="3.1

Ignore the boring SSH error message - Host identification has changed!

The problem If you work with virtual machines in clouds, or you run an SSH server in Docker containers, then you've probably met the following error message during making ssh connection: (I'm connecting through SSH to a docker container) ~$ ssh -p 8822 root@localhost @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is SHA256:smYv5yA0n9/YrBgJMUCk5dYPWGj7bTpU40M9aFBQ72Y. Please contact your system administrator. Add correct host key in /home/jcacek/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home/jcacek/.ssh/known_hosts:107 remove with: ssh-keygen -f "/home/jcacek/.ssh/know

Enable Elytron in WildFly

Steps to enable Elytron in WildFly nightly builds. There is an ongoing effort to bring a new security subsystem Elytron to WildFly and JBoss EAP. For some time a custom server profile named standalone-elytron.xml  existed beside other profiles in standalone/configuration directory. It was possible to use it for playing with Elytron. The custom Elytron profile was removed now.  The Elytron subsystem is newly introduced to all standard server profiles. The thing is, the Elytron is not used by default and users have to enable it in the subsystems themselves. Let's look into how you can enable it. Get WildFly nightly build # Download WildFly nightly build wget --user=guest --password=guest https://ci.wildfly.org/httpAuth/repository/downloadAll/WF_Nightly/.lastSuccessful/artifacts.zip # unzip build artifacts zip. It contains WildFly distribution ZIP unzip artifacts.zip # get the WildFly distribution ZIP name as property WILDFLY_DIST_ZIP=$(ls wildfly-*-SNAPSHOT.zip) # un