Support for byte and short property autoconfiguration?

[alcarraz]

What do you think about implementing @Config for byte fields?

We could add a:

if (c.isAssignableFrom(byte.class) || ...)
    field.set(obj, (byte) 0xff & cfg.getInt(config.value())); 

And maybe something similar, but would involve a for loop, for a byte array property.

Or we could add a default implementation for Configuration.getByte(). And the same for short.

to:

jPOS/jpos/src/main/java/org/jpos/q2/QFactory.java

Lines 458 to 478 in f047169

	if (c.isAssignableFrom(String.class))
	field.set(obj, v);
	else if (c.isAssignableFrom(int.class) || c.isAssignableFrom(Integer.class))
	field.set(obj, cfg.getInt(config.value()));
	else if (c.isAssignableFrom(long.class) || c.isAssignableFrom(Long.class))
	field.set(obj, cfg.getLong(config.value()));
	else if (c.isAssignableFrom(double.class) || c.isAssignableFrom(Double.class))
	field.set(obj, cfg.getDouble(config.value()));
	else if (c.isAssignableFrom(boolean.class) || c.isAssignableFrom(Boolean.class))
	field.set(obj, cfg.getBoolean(config.value()));
	else if (c.isArray()) {
	Class<?> ct = c.getComponentType();
	if (ct.isAssignableFrom(String.class))
	field.set(obj, cfg.getAll(config.value()));
	else if (ct.isAssignableFrom(int.class) || ct.isAssignableFrom(Integer.class))
	field.set(obj, cfg.getInts(config.value()));
	else if (ct.isAssignableFrom(long.class) || ct.isAssignableFrom(Long.class))
	field.set(obj, cfg.getLongs(config.value()));
	else if (ct.isAssignableFrom(double.class) || ct.isAssignableFrom(Double.class))
	field.set(obj, cfg.getDoubles(config.value()));
	}

My motivation is just to lower the boilerplate to configure pinblock formats in a participant. Maybe the byte array support is overkilling, but the plain byte support seems to worth the effort.

The short array may be more reasonable to support easy configuration of MiniGL, layers for example and since we are at it, we can implement all of them.

I'm willing to implement the PR if agreed.

[ar]

Wouldn't hurt, but I don't think of a case where we use 'byte' as configuration. byte[] is probably more useful (assuming a conversion using hex2byte).