> Has anyone used an object database to store Entity beans. Such as object
> store or jasmine. I would be interested to know the implications,
> performance hits etc.
Yes. We are using GemStone/J as EJB server, and we are using it as an object
database at the same time. This is quite easy -- no mapping at all is
necessary. However, you must remember that entity beans are not entities,
i.e. there are objects you store in GemStones object database, and then
there are beans.
There are some more rules to follow, mainly to maintain a consistent view of
GemStone's database across EJB method calls. All this is quite easy and
straight-forward. It is not the most well-documented part of GemStone/J,
though, but even this is improving.
As for performace, we expect better performance with direct GemStone
persistence than collecting our objects from Oracle tables through an OO-ER
mapping middleware. We will start doing systematic concurrent load tests
soon. So far, we're doing quite well.
Ah, by the way, the project is a fairly large (any dimension) insurance app.
Regards,
Hasko Heinecke
Daedalos Consulting
===========================================================================
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".
