Relational objects - an idea

[tobe]

Since it sort of bugs me about implementing the setter for a to-one
relation with the firePropertyChange, I thought perhaps one could
introduce a RelationalObject class in the spirit of the RelationalList.

I think one further benefit of that would possibly be an ability to
implement lazy loading. Also might be useful to break possible
reference cycles.

After that, would it also be possible to remove the requirement to give
the inverse field name?

[Eitan Suez]

i have a number of ideas here.  one of them is to modularize  jmatter:
  to break it up into a number of modules.

i have ideas about improvements to the core that are along the same
lines as what you suggest.  with aspectj, i can get rid of requiring developers
to implement bound properties very easily.

regarding the inverse field name, i'd originally implemented it with a "mental
note" to get back to that later and get rid of it.  the time for this has come.
i'd gladly accept a patch that does away with it for anyone that wants this
done right away.

i've also been thinking (at a fairly high level, nothing concrete just yet) about
a domain specific language for expressing a model.

finally, in the meantime, i've been working on a few intellij idea live templates
that take out some of the redundancy in writing the domain classes.

/ eitan