Sorry, i disagree,
A SSLEndpoint starts it life also as a constructor without a config
object. A LookupLocator is an entity of the same pattern.
Gr. Sim
Patrick Wright wrote:
No, the standard approach would be that the LookupLocator constructor
would take a Configuration object, and the specification/API would
specify which keys would be read from the configuration to configure
the locator. See the APIs for net.jini.discovery.LookupDiscovery, for
example.
Yes, but in order to configure a LookupLocator, you need a constructor to
specifiy in the config file.
like
a.b.c {
socketFactory = new MySocketFactory();
lookupLocator = new LookupLocator("jini://d", socketFactory );
}
instead of (without)
a.b.c {
lookupLocator = new LookupLocator("jini://d" );
}
Gr. Sim
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Leiden: 28088397
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Leiden: 28088397
