[
https://issues.jboss.org/browse/WFLY-7354?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on WFLY-7354:
------------------------------------
{quote}
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.
{quote}
A while back someone had asked a similar question on how to get this working and when I
had checked the code, I did notice it was using TCCL. More details about that here
https://developer.jboss.org/message/962941#962941
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
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.3#72005)