How are the parameters passed by an EJB?

Question

I got a problem on parameters passing of my bean and also got confused.
Let's say my Bean has a method call update(MyObject o);
In the client side, I do
  MyObject obj = new MyObject();
  myBean.update(obj);
  In the bean side, I do
  public void update(MyObject obj) {
    obj.setX(100); // let say this change one of the members of MyObject
  Now, in my client side after the bean update() method call, do I see the changes in MyObject obj? If I do get the changes, the bean must be doing a reverse stub-skeleton call to update my client copy, is that true or I should not assume that?
I was not thinking about all these when developing and the above code works as my assumption in WebLogic 5.1 and 6.0. But, when I port my bean to WebSphere 3.5, the above code crap out -- the client does not see the changes!!
Does anyone know what the inside of this or have any suggestions?

Answer 1

Thanks Jerome, harpreet,
What you two say make sense, however, the problem is still a mystery.
I started developing without thinking of the local copy or remote copy of the parameters between the client and the bean. WebLogic somehow reads my mind and worked the way I wanted (the parameter changes affect the the client copy, how they do that?).
When I finished coding and started porting my bean to WebSphere, I realized beans in WebSphere work in a conceptually different way (parameters are passed by value).
Unfortunately WebSphere works in a kind of logical way but not what I wanted, and WebLogic works magically as I intended but I don't understand how they do it.
So, the question comes down to Are parameters passed by reference or passed by value in EJBs?
If WebLogic passes parameters by reference, is it doing a reverse stub-skeleton call?
If WebSphere passes parameters by value, how can I make it pass by reference?
--Lichu