How to initialize a static final object

Sometimes I need to intitialize a complex static final object, but I don’t like static blocks for initialization. IMHO it isn’t nice to read!
An alternative way is using an static method:

private static final YourObject defaultYourObject = initYourObject();

private static YourObject initYourObject() {
	try {
		return new YourObject(param1, param2);
	} catch (Exception e) {
		// should never happened
		throw new Error("Could not initialize YourObject", e);
	}
}

And of course, the error-handling is an own special topic in this case!

Advertisements

C5Connector.Java Version 0.11

Version 0.11 of the C5Connector.Java has been released.

It’s the Java backend for the filemanager of corefive.

The outstanding feature of this release is that the jar of C5Connector.Java contains the source code of the filemanager. This insures that there aren’t any compatibility issues between C5Connector.Java and the filemanager. We strongly recommend using this feature! The default implementations of the basic interfaces are adapted accordingly.

The changes in detail:

• issue #39: Adapt FilemanagerConfig to Filemanager 2.5.
• issue #40: Integrate the filemanager source into the jar file
• issue #41: New directory with name equals to Parent directory
• issue #43: The default implementation of FilemanagerCapability should respect if a file is protected
• issue #44: updated filemanager to 2.5.0
• issue #45: wrong path in getinfo for folders

 

This could be one of the last releases of this project. The Filemanager project is deprecated. This is why the future of C5Connector.Java is written in the stars.

VPS boot overrides some configuration files

Problem: I bought a new VPS and did some configuration changes (e.g. hostname setting). I’ve installed some software and wanted to test if my settings are boot resistant. And every time the VPS was  booting the files /etc/hosts and /etc/hostname was overridden by the defaults of the provider.

Reason: Virtuozzo (the software which virtualises my VPS) overrides those files at every  time the VPS is booting.

Solution: Replacing the files /etc/hosts and /etc/hostname at boot-time.

The following description is applied for Ubuntu 14.04. Both replacements are implemented as upstart jobs.

/etc/hosts

Copy the /etc/hosts (e.g. /etc/hosts_my) and adapt it to your needs. Then create the file /etc/init/hosts.conf with the following content:

description "restore my hosts"
start on startup
exec cp /etc/hosts_my /etc/hosts

/etc/hostname

Copy the /etc/hostname (e.g. /etc/hostname_mod) and adapt it to your needs. Then edit the file /etc/init/hostname.conf and change the last exec command to:
exec hostname -b -F /etc/hostname_mod
 

That’s it!

C5Connector.Java Version 0.10

Version 0.10 of the C5Connector.Java has been released.

It’s the Java backend for the filemanager of corefive.

Changes of the configuration of the filemanager can cause errors, because the (default) configuration is provided by C5Connector.Java. To ensure a runnable version, the *-bin.zip contains the source of the filemanager.

The changes in detail:

• issue #36: Client and adapter tight coupling (refactored the fetching of the default configuration of the filemanager)
• issue #37: Implementation of ‘baseUrl’ property
• issue #38: Build a bundle with the filemanager source
• updated Jackson to 2.5.4

C5Connector.Java Version 0.9

Version 0.9 of the C5Connector.Java has been released.

It’s the Java backend for the filemanager of corefive.

This is a bug-fix and 3rd-party-update release.

The changes in detail:

• issue #33: Implementation of ‘version’ property
• issue #34: Implementation of the ‘protected’ flag for get-responses
• issue #35: Implement sorting files in ‘getfolder’
• updated Jackson to 2.5.0
• updated slf4j to 1.7.12
• updated servlet-api to 3.1.0

C5Connector.Java Version 0.8

Version 0.8 of the C5Connector.Java has been released.

It’s the Java backend for the filemanager of corefive.

It’s a bug-fix release and mandatory for all who wants to use filemanager 2.0.0:

• issue #30: filemanager.config.js.default isn’t loaded
• issue #32: Adapt FilemanagerConfig to Filemanager 2.0

For more details refer the changelog please.

How to update Lollipop (Android 5.0) on a rooted nexus device

On a rooted nexus device with Lollipop (Android 5.0) the common OTA-updates fails. The reason is: there are some additional security checks while the OTA-update, which fails on rooted devices.

But if you know how to handle the adb-tools, it’s easy to make a manually update. Just download the matching  factory image for your android device and extract the following files: boot.img, recovery.img and system.img.

adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot

That’s it! All your private files won’t be deleted.

I’ve tested it with my nexus 10 and I couldn’t guarantee that this is true for other devices.