[JBoss JIRA] (WFCORE-1998) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1998?page=com.atlassian.jira.plugi... ]
Brad Maxwell reassigned WFCORE-1998:
------------------------------------
Assignee: Osamu Nagano (was: Brad Maxwell)
> Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1998
> URL: https://issues.jboss.org/browse/WFCORE-1998
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 2.2.0.Final
> Reporter: Osamu Nagano
> Assignee: 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)
9 years, 7 months
[JBoss JIRA] (WFCORE-2000) [GSS](7.1.0) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
by Brad Maxwell (JIRA)
Brad Maxwell created WFCORE-2000:
------------------------------------
Summary: [GSS](7.1.0) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
Key: WFCORE-2000
URL: https://issues.jboss.org/browse/WFCORE-2000
Project: WildFly Core
Issue Type: Bug
Components: Modules
Affects Versions: 2.2.0.Final
Reporter: Brad Maxwell
Assignee: Osamu Nagano
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)
9 years, 7 months
[JBoss JIRA] (WFCORE-1998) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1998?page=com.atlassian.jira.plugi... ]
Brad Maxwell reassigned WFCORE-1998:
------------------------------------
Assignee: Brad Maxwell
> Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
> --------------------------------------------------------------------------------
>
> Key: WFCORE-1998
> URL: https://issues.jboss.org/browse/WFCORE-1998
> Project: WildFly Core
> Issue Type: Bug
> Components: Modules
> Affects Versions: 2.2.0.Final
> Reporter: Osamu Nagano
> Assignee: Brad Maxwell
> 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)
9 years, 7 months
[JBoss JIRA] (WFCORE-1999) ConnectionInfo should reflect actual connection informations
by Jean-Francois Denise (JIRA)
Jean-Francois Denise created WFCORE-1999:
--------------------------------------------
Summary: ConnectionInfo should reflect actual connection informations
Key: WFCORE-1999
URL: https://issues.jboss.org/browse/WFCORE-1999
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
Priority: Minor
We have a disconnect between the content of the ConnectionInfo and the command "connection-info". Part of the interface is today unused (information being retrieved from whoami operation).
ConnectionInfo is exposed by CommandContext and could definitely be an interesting piece of information. Usage cleanup and addition of roles should be considered.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 7 months