Ignore missing classes on remote objects
Whi9le loading remote object (by either interface- or standard-lookup) missing clientside interfaces should be ignored and skipped out, since at clientside a service implementation should be able tp feature more than one api set to bind multiple kind of clients.
#3 Updated by achristian over 5 years ago
- Status changed from Assigned to Rejected
- % Done changed from 0 to 100
After more than 2 years, finally found some time to check this. Results:
- Noone else requestes this feature --> not really required?
- Just skipping an interface because of "could ne be loaded" is surely not enough. Who decides which interface IS actually required? Also this feature will complicate programming faults on client-side (forgot to add interface or something like this).
From my point of view: If there are different clients: Create different remote objects (or wrappers), which should not be too complicated thanks to the simon remote annotation.