August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-55) Implement Clean Digest MD5 Mech

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-55?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse moved SASL-51 to ELY-55: ----------------------------------------- Project: WildFly Elytron (was: WildFly SASL Provider) Key: ELY-55 (was: SASL-51) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 1.0.0.Beta1 (was: 2.0.0.Alpha1) > Implement Clean Digest MD5 Mech > ------------------------------- > > Key: ELY-55 > URL: https://issues.jboss.org/browse/ELY-55 > Project: WildFly Elytron > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-49) Unable to build wildfly-sasl using the IBM JDK

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-49?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse moved SASL-67 to ELY-49: ----------------------------------------- Project: WildFly Elytron (was: WildFly SASL Provider) Key: ELY-49 (was: SASL-67) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: SASL (was: Build) Fix Version/s: 1.0.0.Beta1 (was: 2.0.0.Alpha1) > Unable to build wildfly-sasl using the IBM JDK > ---------------------------------------------- > > Key: ELY-49 > URL: https://issues.jboss.org/browse/ELY-49 > Project: WildFly Elytron > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SASL > Environment: java version "1.7.0" > Java(TM) SE Runtime Environment (build pxa6470_27-20131115_04) > IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20131114_175264 (JIT enabled, AOT enabled) > J9VM - R27_Java727_GA_20131114_0833_B175264 > JIT - tr.r13.java_20131113_50523 > GC - R27_Java727_GA_20131114_0833_B175264_CMPRSS > J9CL - 20131114_175264) > JCL - 20131113_01 based on Oracle 7u45-b18 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > The build currently fails with the following error: - > {noformat} > [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ wildfly-sasl --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 3 resources > [INFO] > [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ wildfly-sasl --- > [INFO] Changes detected - recompiling the module! > [INFO] Compiling 47 source files to /home/darranl/src/wildfly/wildfly-sasl/target/classes > [INFO] > [INFO] --- maven-injection-plugin:1.0.2:bytecode (default) @ wildfly-sasl --- > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 3.377 s > [INFO] Finished at: 2014-06-25T11:42:26+00:00 > [INFO] Final Memory: 17M/34M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.jboss.maven.plugins:maven-injection-plugin:1.0.2:bytecode (default) on project wildfly-sasl: Unable to resolve class file path: NullPointerException -> [Help 1] > [ERROR] > {noformat} > As the local testsuite now contains interoperability testing with JDK supplied implementations being able to run the build with other vendors implementations is important. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-50) From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-50?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse moved SASL-11 to ELY-50: ----------------------------------------- Project: WildFly Elytron (was: WildFly SASL Provider) Key: ELY-50 (was: SASL-11) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 1.0.0.Beta1 (was: 2.0.0.Alpha1) > From RFC-2831 a realm name can contain whitespace, this means using space as the delimiter for possible realms is incorrect > --------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-50 > URL: https://issues.jboss.org/browse/ELY-50 > Project: WildFly Elytron > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > > By using space as the separator a single realm name that contains a space is split into two realms. > Either support quoted realm names if they contain a space or choose a different delimiter - (A different delimiter other than a control character may be difficult as the rest can appear in a realm name) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-51) Add a PLAIN SaslClient implementation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-51?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse moved SASL-47 to ELY-51: ----------------------------------------- Project: WildFly Elytron (was: WildFly SASL Provider) Key: ELY-51 (was: SASL-47) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 1.0.0.Beta1 (was: 2.0.0.Alpha1) > Add a PLAIN SaslClient implementation > ------------------------------------- > > Key: ELY-51 > URL: https://issues.jboss.org/browse/ELY-51 > Project: WildFly Elytron > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-52) Add a clean Digest mechanisms implementation

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-52?page=com.atlassian.jira.plugin.sys... ] Darran Lofthouse moved SASL-46 to ELY-52: ----------------------------------------- Project: WildFly Elytron (was: WildFly SASL Provider) Key: ELY-52 (was: SASL-46) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: 1.0.0.Beta1 (was: 2.0.0.Alpha1) > Add a clean Digest mechanisms implementation > -------------------------------------------- > > Key: ELY-52 > URL: https://issues.jboss.org/browse/ELY-52 > Project: WildFly Elytron > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-581) NPE trying to fire a named consequence defined in a parent rule

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-581?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-581. -------------------------------- Fix Version/s: 6.2.0.Beta2 Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/de6bd0d3814ce4064c20868868160... > NPE trying to fire a named consequence defined in a parent rule > --------------------------------------------------------------- > > Key: DROOLS-581 > URL: https://issues.jboss.org/browse/DROOLS-581 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.2.0.Beta2 > > > Trying to fire a named consequence defined in a parent rule the following NPE is thrown > java.lang.NullPointerException > at org.drools.core.definitions.rule.impl.RuleImpl.getNamedConsequence(RuleImpl.java:638) > at org.drools.core.reteoo.RuleTerminalNodeLeftTuple.getConsequence(RuleTerminalNodeLeftTuple.java:165) > at org.drools.core.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1046) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3782) add-user.sh actually does not honor JBOSS_BASE_DIR

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3782?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-3782: ---------------------------------------- Pull requests welcome ;-) But this issue could also use an example command or two to show what you mean - I am not quite following what you say is broken. > add-user.sh actually does not honor JBOSS_BASE_DIR > -------------------------------------------------- > > Key: WFLY-3782 > URL: https://issues.jboss.org/browse/WFLY-3782 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.1.0.Final > Environment: linux > Reporter: David Tonhofer > Assignee: Darran Lofthouse > Fix For: Awaiting Volunteers > > > add-user.sh does not check whether the JBOSS_BASE_DIR points to another directory that the one which can be deduced from JBOSS_HOME assuming the default installation. This may not be what one wants, as one actually wants to update files: > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > instead of > JBOSS_HOME/standalone/configuration/mgmt-users.properties' > JBOSS_HOME/standalone/configuration/mgmt-users.properties' -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3632) @Inject broken for parameterized interfaces

by Alexander Langer (JIRA)

[ https://issues.jboss.org/browse/WFLY-3632?page=com.atlassian.jira.plugin.... ] Alexander Langer commented on WFLY-3632: ---------------------------------------- Created an upstream bug report. > @Inject broken for parameterized interfaces > ------------------------------------------- > > Key: WFLY-3632 > URL: https://issues.jboss.org/browse/WFLY-3632 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Wildfly 8.1.0Final (tested on MacOS X 10.9.3) > Reporter: Alexander Langer > Assignee: Jason Greene > Attachments: CDIMultiModuleTest.zip, CDIMultiModuleTest.zip, server.log > > > @Inject is broken on Wildfly 8.1.0 Final when the interface to be injected is parameterized with a type that extends another type. Example code: > {code} > public interface Foo<T extends Serializable> { } // will fail > public class FooBean implements Foo { } > public interface Bar<T> { } // will work > public class BarBean implements Bar { } > @Singleton > @Startup > public class TestSingleton { > @Inject > private Instance<Foo> foo; > @Inject > private Instance<Bar> bar; > @PostConstruct > public void init() { > System.out.println("##### foo is unsatisfied = " + foo.isUnsatisfied()); > for (Foo f : foo) > System.out.println("foo is: " + f.getClass().getCanonicalName()); > System.out.println("##### bar is unsatisfied = " + bar.isUnsatisfied()); > for (Bar b : bar) > System.out.println("bar is: " + b.getClass().getCanonicalName()); > } > } > {code} > output: > {code} > 22:30:25,904 INFO [stdout] (ServerService Thread Pool -- 50) ##### foo is unsatisfied = true > 22:30:25,905 INFO [stdout] (ServerService Thread Pool -- 50) ##### bar is unsatisfied = false > {code} > The same code works on JBoss AS 7.1.1, so something must have changed for Wildfly. > The attached small example project can be used to reproduce the error. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3782) add-user.sh actually does not honor JBOSS_BASE_DIR

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3782?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-3782: -------------------------------------- Assignee: Darran Lofthouse (was: Tomaz Cerar) > add-user.sh actually does not honor JBOSS_BASE_DIR > -------------------------------------------------- > > Key: WFLY-3782 > URL: https://issues.jboss.org/browse/WFLY-3782 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.1.0.Final > Environment: linux > Reporter: David Tonhofer > Assignee: Darran Lofthouse > Fix For: Awaiting Volunteers > > > add-user.sh does not check whether the JBOSS_BASE_DIR points to another directory that the one which can be deduced from JBOSS_HOME assuming the default installation. This may not be what one wants, as one actually wants to update files: > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > instead of > JBOSS_HOME/standalone/configuration/mgmt-users.properties' > JBOSS_HOME/standalone/configuration/mgmt-users.properties' -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3782) add-user.sh actually does not honor JBOSS_BASE_DIR

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3782?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3782: ----------------------------------- Fix Version/s: Awaiting Volunteers > add-user.sh actually does not honor JBOSS_BASE_DIR > -------------------------------------------------- > > Key: WFLY-3782 > URL: https://issues.jboss.org/browse/WFLY-3782 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Scripts > Affects Versions: 8.1.0.Final > Environment: linux > Reporter: David Tonhofer > Assignee: Darran Lofthouse > Fix For: Awaiting Volunteers > > > add-user.sh does not check whether the JBOSS_BASE_DIR points to another directory that the one which can be deduced from JBOSS_HOME assuming the default installation. This may not be what one wants, as one actually wants to update files: > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > JBOSS_BASE_DIR/configuration/mgmt-users.properties' > instead of > JBOSS_HOME/standalone/configuration/mgmt-users.properties' > JBOSS_HOME/standalone/configuration/mgmt-users.properties' -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2014