> On Feb 18, 2016, at 1:52 AM, Alan Bateman <alan.bate...@oracle.com> wrote: > > > On 18/02/2016 09:08, Weijun Wang wrote: >> OK, but with -providerClass I'd like to support a class name even if it is >> already defined in a module as a service and has its own name. This makes >> sure old commands still work. > I think it should work fine but I assume we would want to discourage this. > That is, these security providers are service provider and there should be no > need for anyone to know the name of the implementation class. >
Exactly. Note that the current ProviderConfig implementation doesn’t support security.provider.N=<classname> if this is loaded from the another named module. It should throw IAE. Mandy
