The problem with C/S mode is that I had to maintain a lot of infrasture code (e.g. the HTTP-server like server engine) that has not much to to with object relational mapping.
It was also quite a lot of work to maintain all changes to the PB kernel in the C/S mode too.
Testing was also very ugly, A single run of the PB testsuite took half an hour...
The PersistenceBrokerBean is an EJB Session Bean that implements the PersistenceBroker interface. The bean is a wrapper an delegates all call to a singlevm PersistenceBroker.
By running this SessionBean in a EJB container you can connect your clients to a remote PersistenceBroker server through standard J2EE EJB mechanisms.
This is completely different from using entity beans.
My experience from the last 2 years is that there is not a single case where it really is a must to use the OJB C/S mode.
SO maybe we should discuss your requirements in details!
cheers, Thomas
[EMAIL PROTECTED] wrote:
hi!
i read some tutorials on ejb and have one question. in my posting some days ago, you told, that the client / server concept will be replaced with
ejb session beans. i told, i just read some ejb tutorials, and have no experience, but why isn't this this done with ejb ENTITY beans?
juergen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
