@David Pilato
Weird! The last time that I looked at that project, it had a note at
the top, "Warning: Project Abandoned". I don't see that now.
It looks like a good project. I don't see the 'RUD' of CRUD in the
test application, but it's probably there. One thing that I am
providing support for is checking the mapping in the index is the same
mapping that the class was designed for, similar to blah</
class> in the persistence.xml file for JPA.
There'll also be hooks for all CRUD methods both pre and post, via
annotations, that will allow extra code in the perisisted class to be
triggered to:
Check additional fields for uniqueness, if you have them, like
emails.
give the ability to do cascading deletes and other more database
like automatic behaviours.
I am going to look more at that code. I was originally going to use
it, but it seemed to have that message I spoke about and my poor
memory says something else wasn't there as a feature.
Anyway, his work is much appreciated, it motivated me to do
something 
PS, it's coming along fine, my programmer is doing quite well. We'll
be doing reflection on the JPA annotations of a class or putting our
own in for the @ID field so that it can be stored. Some other features
are gelling.
On Mar 24, 6:19 am, "David Pilato" da...@pilato.frrote:
Heya,
Did you gave a look at https://github.com/aloiscochard/elasticsearch-osemGitHub - aloiscochard/elasticsearch-osem: ElasticSearch OSEM?
Alois annotation are very complete and close to Compass OSEM annotations.
David.
De : elasticsearch@googlegroups.com [mailto:elasticsearch@googlegroups.com]
De la part de Shay Banon
Envoyé : mardi 20 mars 2012 10:57
À : elasticsearch@googlegroups.com
Objet : Re: Help with the java documentation page
Sure, contributing to the documentation would be great!. For the "osem" like
project, just create a public project on github, we can start from there.
On Mon, Mar 19, 2012 at 1:58 AM, Dennis gear...@gmail.com wrote:
I would like to help edit the content and the english of the Java API.
I am working with making a JPA style connector that works the same way
- osemManagerFactory issues osemManager to do CRUD/S on the store.
It'll be a bit crude at first. I will ask questions of Kimchy here to
get answers, to help my project and understanding of the Java API.
Shay/Kimchy, are you interested in my input on the documentation? Do
you want me to run it by the community here or straight to a private
email with you?
Is the community interested in the code for an 'osemManager' a la'
JPA? Can it be hosted on the site along with Elasticsearch?
).