Would it be possible to get someone from the JDO team to assist in creating a
status sheet on all the different JDO features (caching, extends, depends, long
transactions, lazy loading, etc.) and their respective implementation status?
I believe this would be helpful to all, since due to the high learning curve
associated with figuring out proper castor JDO usage (esp. the mapping), it's
incredibly difficult to tell whether or not problems like this are due to
improper usage, or "not quite done" features.
I am predicting that Bruce Snyder will have absolutely no reply to Ryan
McDonough's question here, other than "This one time at band camp ... please
send your client code and mapping." On the other hand, if Ryan had a place to
quickly and painlessly look up the status of a particular feature (in this
case, dependent objects), he may never resort to such "probing" questions. (I
assume he is probing, trying to quickly find out if this is a well-known issue,
because otherwise he would have sent all his code.) The mailing list archive
is not entirely helpful in this regard, nor is the bugzilla database. What I
have in mind is a one page list of all the major features and their status
("not implemented", "partially implemented", "mostly implemented", "fully
implemented and tested", etc. along with helpful footnotes along the lines of
"works while caching is turned off").
If there is some way to find this information, quickly, please advise. If not,
I hereby volunteer to collect and publish in one place all authoritative
responses to this request as to the status of the JDO features present and
future.
Regards,
Mike Colbert
--- Ryan McDonough <[EMAIL PROTECTED]> wrote:
> I have two objects that have a dependent relationship. It's a MailingList to
> Subscription relationship, a MailingList has many subscriptions. I can add
> Subscriptions to a MailingList and have them persist if the MailingList and
> Subscriptions are created at the same time. However, when I add a new
> Subscription to a MailingList that is already persistent and I update the
> MailingList, the Subscription is not persisted. I have had resort to
> creating each object independently but I would like to use Castor to be able
> to persist a new Subscription when I add it to an existing MailingList. Any
> ideas on what I may be doing wrong?
>
> Ryan-
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
