On 14 May 2008, at 17:42, Christian Schalk wrote:
The only problem with the work I did is that it depends on the model
entities being represented as interfaces and not concrete beans.
Yeah, I recall the discussion. I mainly did this as a tutorial for
fun. I
also did a DB-first approach, as opposed to generating purely from
Java. (In
my former life, I tended to use the DB approach quite a bit. :-)
The SQL script alone might help some none Java folks.
I know that feeling, SQL is nearly always so much faster and easier
to work with... and in production far easier to tune. I started
looking at the person object and all its fields and
relationships.... to share some of the things correctly, like jobs ->
organizations -> addresses, or the potentially wide range of
properties (array of likes)....
The complexity of the full model soon made me go and look at ORM of
some form. Cayenne made sense being a) Apache b) DB friendly c) with
the potential of JPA in the future. Frankly any ORM that had those
features would do. (as would being prepared to write the DDL scripts
and body of SQL for the target db)
Were you thinking of doing more work in this area ? Do you want to
collaborate ?
Sure, would be happy to.
If you get a chance, can you take a quick look at the ORM version at
the link, and see if it makes any sense. I would be fine to focus on
either approach, the main thing in my mind is to get a reasonably
solid RI that can actually be used in small scale production for
those that want to build something off shindig, (small scale probably
== < 1M users ?), but something that will not prevent others
implementing the services and binding to the own more scalable
implementations. Just as Jackrabbit and Pluto started on RI's but did
enough engineering to make them usable as production systems, it
would good to do the same for Shindig (all IMHO). And that coupled
with the fact that I want/need to do this anyway in another open
source project so to me it makes sense to share if possible.
Ian
