[
https://issues.jboss.org/browse/WFLY-7354?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-7354:
-----------------------------------
If someone wants to give a patch to add those two paths, it would be accepted. But this
API isn't really supported by us in any capacity, and furthermore, it is being removed
from Java in Java 9. I suspect that you may have to use the boot classpath to make the
provider work, but I'm not 100% sure. It may use TCCL in which case a module may
work.
Custom NameService by sun.net.spi.nameservice.provider.n doesn't
work on WildFly
--------------------------------------------------------------------------------
Key: WFLY-7354
URL:
https://issues.jboss.org/browse/WFLY-7354
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 10.1.0.Final
Reporter: Osamu Nagano
Assignee: David Lloyd
Attachments: nameserviceProviderTest.zip
System property {{sun.net.spi.nameservice.provider.<n>}} allows a user to customize
a NameService. It works on a standalone java, which is using JBoss Modules, if
{{services="import"}} is added on sun.jdk module dependency and the sun.jdk
module has the following additional dependencies.
{code}
<path name="sun/net/spi/nameservice"/>
<path name="sun/net/spi/nameservice/dns"/>
{code}
Though it doesn't work as a web application which has the same module path and the
same dependency in jboss-deployment-structure.xml.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)