Re: RMIInitialContextFactory

> How about a RMIInitialContextFactory which establishes a new RMIRegistry
> or RMINamingProviderImpl on demand to localhost when first new
> InitialContext call comes. This way I would not have to worry about
> setting up an external naming provider prior to starting my app.

That sounds like a good idea. To maintain backwards compatability we can
alter
RMIInitialContextFactory so that it accepts propertys such as

# defaults to false if not specified and will
# always attempt to create provider
org.realityforge.jndikit.rmi.createProvider=true

# defaults to false if not specified and will
# attempt to create provider if no provider exists
org.realityforge.jndikit.rmi.createProviderOnDemand=true

# defaults to 1977 if not specified
org.realityforge.jndikit.rmi.providerPort=1977

# defaults to false if not specified
org.realityforge.jndikit.rmi.debug=false

So that way the code can either always create provider (ie
org.realityforge.jndikit.rmi.createProvider=true) or have it created if one
does
not already exist (ie
org.realityforge.jndikit.rmi.createProviderOnDemand=true).

Sound good? If so then would you mind sending a patch for this functionality
and I will apply it? :)




-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php