M
Manglu
Hi,
I have a simple HelloWorldApplication which uses SSbs.
I pass a Customer Object which has two attribute String name and
Address address;
I made Address not-serializable
so when i make calls to the SessionBean i get a remote Exception which
contains the not-serializable exception in WebPShere (as expected)
To my surprise this application ran without any problem in JRun4.0
Why would that be the case and what would the result in other APp
Servers like WebLogic be?
AFAIK, objects (parameters and Return types) must be serializable for
all Remote EJB Calls.
Note this applicaiton does not use Local Interfaces..
TIA
Manglu
I have a simple HelloWorldApplication which uses SSbs.
I pass a Customer Object which has two attribute String name and
Address address;
I made Address not-serializable
so when i make calls to the SessionBean i get a remote Exception which
contains the not-serializable exception in WebPShere (as expected)
To my surprise this application ran without any problem in JRun4.0
Why would that be the case and what would the result in other APp
Servers like WebLogic be?
AFAIK, objects (parameters and Return types) must be serializable for
all Remote EJB Calls.
Note this applicaiton does not use Local Interfaces..
TIA
Manglu