Re: [infinispan-dev] Re: property tags in configuration files
OK here is my take.
Populating bean is fairly PITA for a user and a fluent API approach
makes configuration more readable.
http://anonsvn.jboss.org/repos/hibernate/search/trunk/src/test/java/org/h...
(check NotUseddefineMapping)
and the root class
http://anonsvn.jboss.org/repos/hibernate/search/trunk/src/main/java/org/h...
if you want to stay on the bean side, I am wondering why you don't use
JAXB or something like that to bind the XML model to the object model.
On Jun 22, 2009, at 09:47, Vladimir Blagojevic wrote:
We and others already use configuration beans directly (subclasses
of AbstractConfigurationBean) to configure infinispan instances.
However, we "manually" read data from xml and populate those beans
with data. We want to make this reading more automatic via metadata
available in annotations.
On 6/22/09 9:32 AM, Emmanuel Bernard wrote:
> You mean people could actually populate beans themselves to
> programmatically create the InfiniSpan config?
>
> On Jun 22, 2009, at 09:25, Vladimir Blagojevic wrote:
>
>> Hey,
>>
>> We want to use these annotations to create infinispan
>> configuration option documentation directly from the source code
>> as well as to read XML config files and populate corresponding
>> configuration beans with xml data.
>>
>> If we go with expressive annotations we would end up with many
>> many annotations....