Hello,
I am a bit confused about where OJB stands in terms of "auto mapping"
java classes. I am asking because I need to change the serialization
mechanism for a project with a large evolving codebase. As such writing /
changing mapping files everytime the codebase changes is unacceptable;
likewise marking up the code with meta-data (which another tool like xdoclet
could use to generate a map) is also unacceptable. Can OJB automatically
generate mapping files reliably from Java classes? My codebase is such that
it would confuse many heuristics (Castor, for instance, assumes you either
have a pseudo-bean (private vars, public well named getters and setters for
all vars) or pure public access var... in point of fact my codebase does not
entirely adhere to either of these methods (most classes are "partial beans"
where getters/setters might be poorly named...)).
If I am going to have to "roll my own" map generator (a standalone
application) that scans classes it is told to scan, and generates a mapping
file (for OJB or whatever) what is the recommended approach? I was
thinking of going through the SecurityManager... so I could hopefully grant
myself direct access to any kind of variable (and hopefully also be able
to list the variables and their attributes (for instance if they are
transient)). I don't think I could do that with Reflection (I'd have the
same restrictions that arbitrary code would have to member access).
