toby cabot wrote:
>
> danch,
>
> > toby cabot wrote:
> >> I noticed that the remote client code gets a copy of moola but the
> >> server-side session bean gets a reference to the member itself
> >> (and can thus change it).
> >
> > Turn off optimized invocations in jboss.xml
>
> Got it, thank
danch,
> toby cabot wrote:
>> I noticed that the remote client code gets a copy of moola but the
>> server-side session bean gets a reference to the member itself
>> (and can thus change it).
>
> Turn off optimized invocations in jboss.xml
Got it, thanks. I can hack standardjboss.xml for a s
I'm not sure this is valid behavior, but I can't find anything that applies explicitly
to the method return values. This EJB 1.1 spec section on argument values clearly
states that passing method arguments by reference is not allowed so I don't
know why returning a reference should be valid:
18.
toby cabot wrote:
>
> Folks,
>
> I just noticed the following behavior and wonder if there are preferred
> patterns for dealing with it. I've got an entity bean which can
> presumably be accessed by remote client-side code (e.g. in another VM)
> or by session beans running in the jboss server
