[
https://issues.apache.org/jira/browse/GERONIMO-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537021
]
Vasily Zakharov commented on GERONIMO-1804:
-------------------------------------------
It seems this issue is no longer actual, as the necessary customization may now
be easily performed in var/config/config.xml. For example, for Apache Harmony:
<gbean name="NamingProperties">
<attribute
name="namingFactoryInitial">org.apache.harmony.jndi.provider.rmi.registry.RegistryContextFactory</attribute>
<attribute
name="namingFactoryUrlPkgs">org.apache.harmony.jndi.provider</attribute>
<attribute name="namingProviderUrl">rmi://${ServerHostname}:${NamingPort +
PortOffset}</attribute>
</gbean>
So, I'm suggesting to close this issue as FIXED.
> The name of JNDI/RMI service provider is hardcoded in the sources.
> ------------------------------------------------------------------
>
> Key: GERONIMO-1804
> URL: https://issues.apache.org/jira/browse/GERONIMO-1804
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: JVM-compatibility
> Affects Versions: 1.0
> Reporter: Andrey Pavlenko
> Attachments: StaticJndiContextPlugin.patch
>
>
> The name of the initial context factory is hardcoded in the sources, so it
> might not work on non-Sun VMs.
> The attached patch customizes the name of the initial context factory in the
> following way:
> It attempts to find NamingProperties GBean in the kernel.
> if the GBean is found all required naming properties are obtained from
> GBean's attributes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
