Přeskočit na hlavní obsah

Výčtový typ pro starší Javu

Už několikrát jsem přemýšlel nad tím, že bych měl na stránky občas přidávat i věci týkající se mé práce, tedy hlavně javy. Ještě musím vymyslet, jak vkládat kód hezky s barvičkama, ale to přijde ;).

Včera se mě ptal jeden bývalý spolužák, jak udělat správně výčtový typ ve starší Javě. Tak jsem mu poslal následující příklad, který jsem okoukal v knize Java Efektivně.

Poté, co si kód prošel, prohlásil:

ty jo, zase jsem o neco chytrejsi
ted jsem se naucil, jak napsat vec, co jsme driv delali pomoci konstant na dva radky, tak jak ji napsat na radku 100!
uplne mam pocit, ze jsem postoupil do dalsiho levelu ;)
import java.io.Serializable;
import java.util.HashMap;
import java.util.Map;

/**
* Implementace vyctoveho typu v jave 1.4 a starsi.
* @author Josef Cacek
*/
public final class AppState implements Serializable {

  private static final long serialVersionUID = -4346433248901502211L;

  private String name;
  private static Map allStates = new HashMap();

  public static final AppState NEW = new AppState("NEW");
  public static final AppState ASSIGNED = new AppState("ASSIGNED");
  public static final AppState INPROGRESS = new AppState("INPROGRESS");
  public static final AppState CLOSED = new AppState("CLOSED");

  /**
   * vypnout default contructor
   */
  private AppState() {
    throw new IllegalStateException();
  }

  /**
   * Kontruktor, ktery potrebujem.
   * @param aName jmeno stavu
   */
  private AppState(final String aName) {
    if (aName==null) {
      throw new NullPointerException("State name can't be null.");
    }
    name = aName.toUpperCase();
    if (allStates.containsKey(name)) {
      //kdybychom se zapomneli
      //a pri copy paste nezmenili parametr konstruktoru
      throw new IllegalArgumentException("State with name '"
          + name + "' already exists.");
    }
    allStates.put(name, this);
  }

  /**
   * Vraci soucasny stav
   * @return stav jako String
   */
  public String getName() {
    return name;
  }

  /* (non-Javadoc)
   * @see java.lang.Object#toString()
   */
  public String toString() {
    return getName();
  }

  /**
   * Vraci stavovy objekt pro dane jmeno
   * @param aName jmeno stavu
   * @return stav
   */
  public static AppState valueOf(final String aName) {
    if (! isState(aName)) {
      throw new IllegalArgumentException("Wrong state name - '"
          + aName + "'.");
    }
    return (AppState) allStates.get(aName.toUpperCase());
  }

  /**
   * Vraci jmeno stavu v parametru
   * @param aState stav
   * @return jmeno stavu (nebo null, jestlize parametr je null)
   */
  public static String toString(final AppState aState) {
    return aState==null?null:aState.toString();
  }

  /**
   * Vraci true jestlize existuje stav s danym jmenem.
   * @param aName jmeno stavu
   * @return true, kdyz existuje stav s danym jmenem
   */
  public static boolean isState(final String aName) {
    return aName!=null && allStates.containsKey(aName.toUpperCase());
  }
}

Komentáře

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...

Simple TLS certificates in WildFly 18

It's just 2 weeks when WildFly 18 was released. It includes nice improvements in TLS certificates handling through ACME protocol (Automatic Certificate Management Environment), it greatly simplifies obtaining valid HTTPS certificates. There was already a support for the Let's Encrypt CA in WildFly 14 as Farah Juma described in her blog post last year. New WildFly version allows using other CA-s with ACME protocol support. It also adds new switch --lets-encrypt to interactive mode of security enable-ssl-http-server JBoss CLI commands. Let's try it. Before we jump on WildFly configuration, let's just mention the HTTPs can be used even in the default configuration and a self-signed certificate is generated on the fly. Nevertheless, it's not secure and you should not use it for any other purpose than testing. Use Let's Encrypt signed certificate for HTTPs application interface Start WildFly on a machine with the public IP address. Run it on the defaul...

JSignPKCS11 - when your smartcard is too smart

TL;DR Yes, you can add digital signatures in Java even when you use newer hardware tokens such as Gemalto SafeNet eToken 5110 CC. JSignPKCS11 might help. Maybe you've seen the infamous PKCS11 error message CKR_USER_NOT_LOGGED_IN already. Thrown even when the SunPKCS11 security provider and the keystore settings were properly configured for your hardware token. java.security.ProviderException: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_USER_NOT_LOGGED_IN at jdk.crypto.cryptoki/sun.security.pkcs11.P11Signature.engineSign(P11Signature.java:685) at java.base/java.security.Signature$Delegate.engineSign(Signature.java:1404) at java.base/java.security.Signature.sign(Signature.java:713) ... Caused by: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_USER_NOT_LOGGED_IN at jdk.crypto.cryptoki/sun.security.pkcs11.wrapper.PKCS11.C_Sign(Native Method) at jdk.crypto.cryptoki/sun.security.pkcs11.P11Signature.engineSign(P11Signature.java:664) ...