> As Dan pointed out, this is in the spec.
see my answer to that. If developers screw up the current design dies (!)
and with the Dan proposal we don't deploy... with the new stuff, we don't
die and we deploy. (bonus: constant speed, fast in every case, even the
screw ups) And of course we are still 100% kosher in all cases <grin>.
> How do you ensure a unique identifier?
just like you did the SSB
> Also, remember that the mapping between real PK and jBoss PK must be
> persistent. With CMP we can simply add it as a column, but how do you
> intend to solve this for BMP??
No it doesn't need to be persistent.
The fastKey is just a way for the cache to say... here next time you come
back don't bother just use this key. It is a run-time thing. It signifies
the association of an EJBObject and the cache context... it is not the
association of an EJB to an instance, as is currently done, see?
> > no offense, but clearly a superior design :))
>
> That remains to be seen. I will be impressed if you have decent answers
> for the above show-stoppers. ;-)
what show stopper :)))
>
> > Listen Rickard, I will rewire this, but it might be deeper than
> we think (I
> > basically need to retool the way the lookups are done everywhere :((()
>
> As usual, don't rewire until we know it is a good thing to do...
doing it...doing it...
it's pretty simple too
marc
"your hands are numb, so your head will miss this" (some rap song I am
listening too...)
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
