Bug #14
don't prepare methods for remote calling if arguments, return types or exceptions are not serializable
| Status: | New | Start: | 09/30/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Jörg Plewe |
% Done: | 0% |
|
| Category: | Weaving | |||
| Target version: | 0.5.4 |
Description
If any of the arguments, return types or exceptions of a method are not serializable, it doesn't make much sense to try remote calling.
Issue a warning and don't weave in anything.
Note that testing declared 'Serializable' is necessary but not sufficient.
History
Updated by Jörg Plewe over 2 years ago
Static type checking is not sufficient, bc. declared serializability (what a word) doesn't count. The actual objects need to be checked at runtime
- which cannot be done for return types
- which cannot be done for exceptions
- waiting for a NotSerializableException is equivalent with an explicit analysis?
Updated by Philipp Haußleiter about 2 years ago
- Target version set to 0.5.4