The service api is the interface or interfaces implemented by the service proxy and used by the client. These interfaces are installed on the client, they're not dynamically downloaded.
For example, the service api for com.sun.jini.reggie.RegistrarProxy is made up of the following mix in interfaces: net.jini.core.lookup.ServiceRegistrar, net.jini.admin.Administrable, net.jini.id.ReferentUuid The proxy class itself is package private and is not visible to the client. Smart proxy implementation classes are free to use generics, provided they're not included in the service api. Service api is a compile time boundary. Cheers, Peter. ----- Original message ----- >From Simon IJskes - QCG <si...@qcg.nl> Sent: Wed, 3 Oct 2012, 17:47:24 GMT-10 To dev@river.apache.org Subject Re: generics > On 03-10-12 00:42, Peter wrote: > > Don't forget that due to erasure, it isn't possible to support generics in > > service api. > > > > Anything outside of service api is however. > > To be concrete, what is the service api? (in package or class names?). > > > > -- > QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl > Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
