This one time, at band camp, Thorsten van Ellen said:
TvE>Mapping objects to a database with JDO has no requirements
TvE>for the class, e.g. there is no interface implementation required.
TvE>This is a great deal! I can focus on the business code!
TvE>
TvE>But I am still curious about how it works?
TvE>As far as I understand it, it must work with java reflection,
TvE>but even private fields can be mapped!
TvE>This means to me: JDO must have special access
TvE>otherwise the security manager would complain.
TvE>
TvE>Can anybody tell me: do I have to make any provisions
TvE>(especially for the security) to enable JDO to work?
Thorsten,
Castor will not work against private member fields of objects because
of the security implications and playing nice with security managers.
As long as your data objects are JavaBean-like, everything will work
just fine.
I prefer Dennis Sosnoski's description of JavaBean-like from his article
called 'Data Binding with Castor':
-------------------------------------------------------------------
So what does "JavaBean-like" mean? Real JavaBeans are visual components that
can be configured within development environments for use in GUI layouts. Some
practices that began with real JavaBeans have since become widespread in the
Java community, especially for data classes. I call a class "JavaBean-like" if
it follows these practices:
* The class is public
* It defines a public default (no argument) constructor
* It defines public getX and setX methods for access to property (data) values
-------------------------------------------------------------------
Take a look at the articles listed on the following page in order to
understand and get started with Castor:
http:/www.castor.org/presentations.html
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
