![](https://d3ilqtpdwi981i.cloudfront.net/swnGi26_-w9BnaUT-GZBWQEjb5A=/425x550/smart/https://bepress-attached-resources.s3.amazonaws.com/uploads/20/14/37/20143732-46d6-46f3-8aad-06dda1bca663/thumbnail_0cc89ae3-ba49-4f6e-ab85-80a1f0161635.jpg)
The CentiJ system synthesizes Java source code that funnels invocations through an RMI (Remote Method Invocation) based transport layer for distributed computation. The technique generates bridge pattern code (i.e., interfaces and proxies) that automate the creation of virtual proxies for message forwarding. We examine the tradeoffs between bridge implementations based on manual static delegation, automatic static delegation, and dynamic proxy classes. Advantages of the CentiJ technique include improved performance, type safety, transparency, predictability, flexibility and reliability. We then look at various methods for solving the disambiguation problem that arises when delegates have conflicting method signatures. Disambiguation can be automatic, semi-automatic or manual. CentiJ can automatically create a class that alters the interface to the bridge (using the adapter pattern).
Available at: http://works.bepress.com/douglas_lyon/13/
Copyright 2002 Journal of Object Technology
Archived with permission from the copyright holder.