/explore
|
You are here 
|
dzone.com | ||
| | | | |
blog.pchudzik.com
|
|
| | | | | ||
| | | | |
mustafaali.net
|
|
| | | | | [AI summary] The article explains security risks in Kotlin data classes where sensitive information like passwords leaks automatically in toString() output and provides three coding solutions to prevent data leakage. | |
| | | | |
ryanharter.com
|
|
| | | | | Value types in Java are hard. Well, not hard, but tedious. Google's AutoValue library makes them much easier and has just received the long awaited update that adds the flexibility of extensions. Value Types in Java Before we can talk about how great AutoValue is, let's look at the problem it solves: value types. A value type is simply an immutable objects whose equality is based on property values, as opposed to identity. | |
| | | | |
www.craigpardey.com
|
|
| | | Spring 3.2 has some very nice features for scheduling tasks. The pure Java way of doing this looks something like private ScheduledExecutorService executor = Executors.newSingleThreadScheduledExecutor(); class ScheduledTask implements Runnable { @Override public void run() { System.out.println("Running scheduled task"); } } // Schedule a task every 5 seconds executor.scheduleAtFixedRate(new ScheduledTask(), 1, 5, TimeUnit.SECONDS); // If you don't do this then the JVM won't exit cleanly executor.shutdown(); But now, with the snazzy new Spring scheduling annotations, it can be as simple as this | ||
