[JBoss JIRA] (WFLY-7354) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-7354?page=com.atlassian.jira.plugin.... ]
David Lloyd reassigned WFLY-7354:
---------------------------------
Assignee: (was: David Lloyd)
> 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.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-7354) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly
by David Lloyd (JIRA)
[ 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)
9 years, 6 months
[JBoss JIRA] (SECURITY-903) Differently implemented password-stacking option in ClientLoginModule
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/SECURITY-903?page=com.atlassian.jira.plug... ]
RH Bugzilla Integration commented on SECURITY-903:
--------------------------------------------------
Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1254194|https://bugzilla.redhat.com/show_bug.cgi?id=1254194] from MODIFIED to ON_QA
> Differently implemented password-stacking option in ClientLoginModule
> ---------------------------------------------------------------------
>
> Key: SECURITY-903
> URL: https://issues.jboss.org/browse/SECURITY-903
> Project: PicketBox
> Issue Type: Bug
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Fix For: PicketBox_5_0_0.Alpha2
>
>
> From BZ:
> "In case when some login module should use password stacking then value of password-stacking option should be set to useFirstPass. All login modules should respect it. However implemetation of org.jboss.security.ClientLoginModule uses password-stacking differently - it uses password stacking everytime when some value is set for password-stacking option (even value false). It should work same as other login modules. Current behavior can be confusing and can lead to incorrectly set server configuration."
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFLY-3578) jboss-cli.bat always exits with return code 0 even after a cli failure
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3578?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3578:
-----------------------------------------------
Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1223877|https://bugzilla.redhat.com/show_bug.cgi?id=1223877] from MODIFIED to ON_QA
> jboss-cli.bat always exits with return code 0 even after a cli failure
> ----------------------------------------------------------------------
>
> Key: WFLY-3578
> URL: https://issues.jboss.org/browse/WFLY-3578
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: 8.1.0.Final
> Environment: Windows
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 9.0.0.Alpha1
>
>
> jboss-cli.bat cannot be reliably controlled by other scripts because it does not report return code from cli execution and always exits with 0 even after a failure.
> It can be solved with the following patch:
> {noformat}
> --- C:/home/JBoss/wildfly-8.1.0.Final/bin/jboss-cli-orig.bat Sat May 31 04:54:25 2014
> +++ C:/home/JBoss/wildfly-8.1.0.Final/bin/jboss-cli.bat Thu Jul 03 10:19:09 2014
> @@ -1,4 +1,5 @@
> @echo off
> +setlocal ENABLEEXTENSIONS
> rem -------------------------------------------------------------------------
> rem JBoss Admin CLI Script for Windows
> rem -------------------------------------------------------------------------
> @@ -48,6 +49,7 @@
> if not exist "%JBOSS_RUNJAR%" (
> echo Could not locate "%JBOSS_RUNJAR%".
> echo Please check that you are in the bin directory when running this script.
> + set /A RC=1
> goto END
> )
>
> @@ -71,5 +73,11 @@
> org.jboss.as.cli ^
> %*
>
> +set /A RC=%errorlevel%
> :END
> if "x%NOPAUSE%" == "x" pause
> +
> +if "x%RC%" == "x" (
> + set /A RC=0
> +)
> +exit /B %RC%
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months
[JBoss JIRA] (WFCORE-102) Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-102?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-102:
------------------------------------------------
Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1299102|https://bugzilla.redhat.com/show_bug.cgi?id=1299102] from MODIFIED to ON_QA
> Remove the need for OSH authors to deal with ServiceVerificationHandler or removal of installed services in rollback
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-102
> URL: https://issues.jboss.org/browse/WFCORE-102
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha9
>
>
> The various base classes OSH authors use to create handlers force the author to deal with ServiceVerificationHandler and, during rollback, with removing any services the OSH added. This task is to have the OperationContext handle these things transparently, removing the need for authors to do so.
> To preserve compatibility, the various API methods authors may have overridden that expose the SVH and the list of added ServiceControllers will be retained (but deprecated), but the SVH and the list of handlers won't be used. The API javadoc will encourage use of method variants that don't use these parameters.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 6 months