Sean Landis wrote:
I *am* sensitive to the notion of compatibility but I would argue that no effort should be spent creating a compatibility layer for the com.sun.jini classes. It has historically been made perfectly clear that the developer depends on these classes at his/her peril. There is plenty of work to do and I do not think time should be spent on this.
For some APIs in com.sun.jini there might be value in a compatibility layer such as the starter framework among other things people often refer to in configuration files. For most of the classes though in com.sun.* I don't think there is much reliance on (these are merely the implementation details for the net.jini API or represent the contributed services). I also don't know whether a compatibility layer can be a 100% solution without getting into a complete code duplication effort and to what extent it introduces its own set of problems. Personally I don't have much interest in such a layer, but maybe others have and did an assessment what is required and can provide a more informed opinion on this matter and whether they would also help to implement and maintain it. -- Mark
