[EMAIL PROTECTED] writes:
> On Oct 18, Aaron Mulder quoth:
[snip]
> I would implore anyone interested in this topic to go back and read the
> back and forth Tom White and I had on this very issue a couple of weeks
> ago. Offering a default ID service in jboss isn't a simple "yeah we
> should have that" type decision. There is no "right" answer to this
> question and by providing a solution in the distribution you will be
> endorsing a specific solution that will be used without the developer
> considering it's applicability.
Cook. Tom Cook.
> I fully support the notion of people writing database specific mbeans (or
> whatever) to provide this functionality but think it would be a Bad
> Idea(tm) to provide it in the distribution. Encourage people to build
> appropriate solutions for different problems rather than a
> one-solution-fits-all in the distribution. Then provide a FAQ reference
> so people can fetch the Postgre or Oracle, integer or long, standalone or
> clustered, A or B, this or that version of the mbean as is
> appropriate.
Agree with you there.
> A primary key service *is* appropriate for the container but it is *not*
> appropriate for the container manufacturer. Such a decision is very
> application and domain specific.
Also if you make jboss provide the keys for _all_ applications then
you loose the association between the data and the mechanism which
ensures it's consistency. Now a non-ejb app can't use the same
mechanism. People should design key generators for their apps.
Tom
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
