Jochen,
Accorrding to the J2EE blueprints, entity beans should not be accessed directly
from the client. Maybe you can take a look at a session bean facade that they
are using in the java petstore example in the J2EE blueprints. They make a model
object that is serializable and just holds the data of their entity beans. They
then have session beans that the client can call to deal with these models. It
works nicely and removes all those remote calls (you know for each set/get) and
database calls.
Maybe that helps,
John
jochen mader wrote:
> Hey,
> I've been browsing through the archive of this mailinglist and it seems like
> that there are more people than me who have a quite similar problem.
> We are currently creating many thousand beans per hour (aprox 13000). That is
> no problem, jonas works perfectly for that. The problem is now that as soon
> as we start to work with the beans the whole thing gets REALLY slow (just to
> get an integer from a bean takes about a second), but that is not the real
> problem. After two or more clients try to use the beans the whole memory
> fills up until the thing crashes (each client needs around 10000 beans per
> request). I played around with transactions, the querys ... (as described in
> the mailinglist) and I came to the conclusion that there must be something
> wrong with jonas. Or is the entitybean-support to be considdered experimental
> (as stated in another posting to this list I read)?
> Has anybody in this list solved that problem???
>
> Regards
> Jochen
>
> P.S.: We just switched to Jonas 2.1.1.
> ----
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body of the message "unsubscribe jonas-users".
> For general help, send email to [EMAIL PROTECTED] and
> include in the body of the message "help".
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
