Dan OConnor writes:
> On 18 Oct 00, at 15:26, [EMAIL PROTECTED] wrote:
[snip]
> (1) An EJB-component based solution as Rickard has advocated
> (and for which he has provided a prototype).
>
> (2) A persistence-manager based solution for container-managed
> persistence. This solution would, of course, be database-specific.
> Here I like the role that an MBean can play. In other words, the
> persistence manager could look for a database-specific MBean to
> which it could delegate the sequential primary key management.
>
> I'm very sure that #1 is a good idea. I would like to provide support
> in the persistence manager for CMP entities with sequential keys,
> so I think that #2 might also be a good idea. But I haven't
> prototyped it, nor have I spent more time thinking about it than it
> took me to type it. So I'd love to hear some feedback.
Mmm, I'm not convinced. Consider somebody constructing an EJB app
around some legacy system. Now, with #2, CMP becomes more or less
unusable because we want to stick with some primary key scheme from
our legacy app. With #1 at least you have the option of not using
it, but I'm still not convinced it's a Good Thing. People should
think about data consistency, not just assume that some service they
heard about once will take care of it...
Tom
--
Tom Cook - Software Operations
"We rarely find that people have good sense unless they agree
with us."
- Francois, Duc de la Rochefoucauld
LISAsoft Pty Ltd - www.lisa.com.au
--------------------------------------------------
38 Greenhill Rd. Level 3, 228 Pitt Street
Wayville, SA, 5034 Sydney, NSW, 2000
Phone: +61 8 8272 1555 Phone: +61 2 9283 0877
Fax: +61 8 8271 1199 Fax: +61 2 9283 0866
--------------------------------------------------
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
