This one time, at band camp, Bert van Brakel said:
BvB >Will future versions of castor support proxy objects, if they are not
BvB >currently supported? I guess I could make a seperate object sharing the same
BvB >table as the proxied object, and then have the proxy object call castor to
BvB >get the full object, but it makes it that much more messy
Bert,
At this time, Castor does not support proxy objects. It's a great
idea and one that has been discussed in the past. Unfortunately
adding this to the current architecture involves quite a lot of
work.
Your design seems quite good and possibly doable, not to mention
something that's really needed. It would be quite nice to execute a
query and have a collection of proxy objects returned that are only
materialized upon request.
Since you've already thought through some of this design, I would
encourage you to begin implementing it. Please remember to develop
a set of test cases using the JUnit based test framework that is
located in src/tests. Test cases are an important part of moving
Castor forward because they provide a method for reliable, reproducable
and consistent testing of such a complex feature, but also saves
the Castor maintainers an *awful* lot of work.
--
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
