lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Male (Updated) (JIRA)" <>
Subject [jira] [Updated] (SOLR-2708) Allow customizable bean mapping for QueryResponse.getBeans(..)
Date Mon, 26 Mar 2012 02:46:26 GMT


Chris Male updated SOLR-2708:

    Attachment: SOLR-2708.patch

Updated patch.

This patch really changes how DocumentObjectBinder works, trying to make it more OO and extendable.

Major changes included:
- ExtendedType notion which isolates much of the messy dealing with reflection stuff
- DocumentValue which provides an extensible and OO driven way of reading and writing values
- BeanProperty which abstracts field and method property access

Embedded property support is included.

Some undocumented hacks have also been removed.
> Allow customizable bean mapping for QueryResponse.getBeans(..)
> --------------------------------------------------------------
>                 Key: SOLR-2708
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: clients - java
>    Affects Versions: 1.4, 3.1
>            Reporter: Bozhidar Bozhanov
>         Attachments: SOLR-2708-beanProperty-valueBinder.patch, SOLR-2708-beanProperty.patch,
SOLR-2708.patch, SOLR-2708.patch, SOLR-2708.patch, SOLR-2708.patch
> The mechanism for getting beans is rather limited - only classes @Field-annotated fields.
> Imaging the following subprojects:
> - common
> - search
> And you want to reuse a class from common as a result from a solr search. You should
either duplicate the structure or make common depend on solrj. Neither are desirable.
> So, my suggestion:
> - introduce a pluggable mechanism for bean resolution. Currently it is impossible - it
uses private methods and private inner classes. (This will be useful for custom conversions,
because the existing one fails in some cases where BeanUtils.copyProperties works.)
> - allow externalized (xml) configuration
> - allow detecting all fields, annotated or not (off by default)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message