Hi,
I have just committed a few changes to the I/O API, and also the
extensions that store data on disk.
For the I/O API, it now uses more flexible generics to allow Inputs and
Outputs that don't strictly match each other to be used together. For
example, let's say you have an Input with Strings, and an Output for
Objects. Before you would have to transform the Strings to Objects to
get this to work, but now it works as-is, since String is a subclass of
Object.
For the entitystores, and also RDF Native Repository, I have added
support for the FileConfiguration service. If the FileConfiguration
service is available all those services will figure out where to store
data by using "new File(fileConfiguration.dataDirectory(), serviceId)".
This way there is no need to explicitly configure them as to where to
store the data.
To preserve backwards compatibility this will only occur if the
FileConfiguration service is used, otherwise the old style (=manual
configuration or reasonable defaults) is used. For most cases I would
strongly recommend using the FileConfiguration service though.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
