Many ways of solving this of course. Some are the ways you said.
The more easy ones though.
If you lock inte one DB, you can use the DB's way of creating ids. For
example MS SQL Server use the identity functionality and be sure never to
change the id member. This will work also with CMP.... I belive. You will
overwrite the the id column when you do a refresh but I think I remember
that that was alright.
Another way is to use an entity EJB, which generates an id, which will be
clusterable and doesn't have a big performance impact.
<ad>
There is an opensource component for this very soon at www.backsource.org,
but it hasn't been released yet, or actually the webadministrator hasn't
bothered to put it in yet. I you are interested you can mail me and I'll
send it to you.
</ad>
Regards
Erik Romson
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
