Originally posted by Thomas Paul:
But just because the week is over doesn't mean you have to go away, Matjaz.
Originally posted by Rajeev Gupta:
As far as it concern with implementing both the interface, The Virtual machine will have a problem as to transffer an object with what techinque(Serialization or Remote).
Originally posted by Thomas Paul:
It would appear that this can only work if the client has access to the remote object class itself and not just the remote interface. Perhaps that is why Serializable/Remote is used in the java.rmi.server package?
Originally posted by Doug Wang:
What if a Remote object itself acts as a parameter to pass across machines?
Originally posted by Thomas Paul:
I got a clean compile and a clean rmic on this:
Originally posted by Aftab:
But in my code I want to find by workflowcode and eventname(instead of eventcode). How should I do this with CMP?? My EJB book says this is vendor specfic for each App server. But does explain how it is done. With BMP this would be straightforward..you just write JDBC code for each finder.
Originally posted by Bill Bailey:
On what "tool" are these examples based.
Are they vendor independant, or did you choose to use WebLogic, Websphere, Oracle 9iAS.... with the specificities it can sometimes imply ?
Originally posted by Thomas Paul:
This is incorrect. Look at the RemoteObject class which is in the package java.rmi.server:
http://java.sun.com/j2se/1.3/docs/api/java/rmi/server/RemoteObject.html
It implements both Remote and Serializable.
Originally posted by Dieter Cailliau:
Where i really need an answer is: what happens if one entity bean (with pk "12") is accessed by two clients, and all it's methods are transaction required. Are two threads going toghether over the bean, and is the transaction enforced in the database by the database mechanisms, or is it the j2ee container who denies access to the second thread because it knows the first thread is in transaction?[/URL]
Originally posted by Rulin Yang:
If I use URL/URLConnection, I have to do some code in the server side to read InputSteam and write outStream. I am not sure how I can do it. My legacy system my not allow me to do any coding.
Originally posted by Dieter Cailliau:
Why is an ejb non-re-entrant by default? What's the good thing about this restriction? I don't see the point, i would never have thought about "hey maybe we could provide a mechanism that disallows ejb A to call back itself with another ejb in between". So what?