hutdev/jprom

A library for mapping Java property files to objects

jprom's Issues

Allow unmarshalling of several types in a single function call

Currently a call of PropertyUnmarshaller.unmarshal is needed for each type that needs to be unmarshalled from property data. Find a way to unmarshal several types from property data in a single function call.

Allow marshalling of stray objects

Currently each object needs to be wrapped in a Collection before it can be passed to PropertyMarshaller. Provide a method that allows passing single objects to the PropertyMarshaller.

Allow definition of type converters

Currently only target types with String constructors are supported. It should be possible to implement custom type converters and add them to the (at)Property annotations to support custom types.

Also, some Classes with String constructors can behave unexpectedly, e. g. Locale:
Locale.GERMANY.toString() == "de_de"
new Locale("de_de") != Locale.GERMANY

Tasks:

1. Define a converter interface
2. Define an annotation parameter in (at)Property to bind a converter implementation to a field.

Create utility classes to simplify usage

E. g. : JPromUtils.read(clazz).from(input)

Replace hut.jprom.NoOpCombiner with operational combiner methods

Create operational combiner methods. No op combiners might not be supported in future Java versions.

Direct use of getter and setter methods when un/marshalling

PropertyUnmarshaller and PropertyMarshaller currently use hut.jprom.PropertyProcessor.getPropertyFields to obtain information about annotated fields. Holding information about the getter and setter methods (e. g. via two methods getPropertyGetters and getPropertySetters) could improve performance.

Scan classpath for classes annotated with (at)PropertyRoot

Unmarshalling could be simplified by classpath scanning. This way it would not be necessary to pass the target classes to the unmarshalling methods. Cf. #7

ResourceBundle support

Jprom could be used for easy management of ResourceBundles for i18n purposes.

Integration of asm for faster analysis of annotated types and fields

Use ASM for faster analysis of annotated types and fields instead of the reflection API.