November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7285) Elytron - inconsistency between DMR and XSD representation of simple-permission-mapper

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7285?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-7285: ----------------------------------- Fix Version/s: 11.0.0.Alpha1 > Elytron - inconsistency between DMR and XSD representation of simple-permission-mapper > -------------------------------------------------------------------------------------- > > Key: WFLY-7285 > URL: https://issues.jboss.org/browse/WFLY-7285 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Optional > Labels: user_experience > Fix For: 11.0.0.Alpha1 > > > There are inconsistencies between DMR and XSD representation of {{simple-permission-mapper}}. > According to XSD both {{permission-mapping}} [1] and its inner {{permission}} [2] must occur at least one times in {{simple-permission-mapper}}. According to DMR they are {{"nillable" => true}}. This should be unified. > [1] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... > [2] https://github.com/wildfly-security/elytron-subsystem/blob/82a3cfb2c1c7c8... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1952) Change byteman listening port to avoid conflicts with TeamCity

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-1952: ----------------------------------------- Summary: Change byteman listening port to avoid conflicts with TeamCity Key: WFCORE-1952 URL: https://issues.jboss.org/browse/WFCORE-1952 Project: WildFly Core Issue Type: Enhancement Components: Test Suite Affects Versions: 3.0.0.Alpha11 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor Tests using Byteman have it listening on port 9091 that may be used by Team City for its agents. We need to change this port value in the poms. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1951) Expose content repository read-content as a GET operation

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-1951: ----------------------------------------- Summary: Expose content repository read-content as a GET operation Key: WFCORE-1951 URL: https://issues.jboss.org/browse/WFCORE-1951 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.0.Alpha11 Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Allows the use of the GET method to obtain the binary stream to a content in the content repository. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6854) Upgrade Hibernate ORM to 5.1.3

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-6854: ------------------------------------ We should also upgrade Javassist to 3.20.0-GA, which Netty + Hibernate ORM 5.1.x is using. > Upgrade Hibernate ORM to 5.1.3 > ------------------------------- > > Key: WFLY-6854 > URL: https://issues.jboss.org/browse/WFLY-6854 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Emmanuel Bernard > Assignee: Scott Marlow > Fix For: 11.0.0.Alpha1 > > > This is a follow up on WFLY-6682. > After looking at the list of potential incompatibilities, we decided to not upgrade to 5.2 but instead to 5.1 to provide a smoother experience to users. > We can consider adding a 5.2 optional switch via Jipijapa if bandwidth permit but let's treat it as a second issue and have [~smarlow] lead it. > PS: I put v11Alpha1 but feel free to adjust it to any WF 11 version that fits best. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7508) EE Concurrency tasks continue running after a deployment has been removed

by James Perkins (JIRA)

James Perkins created WFLY-7508: ----------------------------------- Summary: EE Concurrency tasks continue running after a deployment has been removed Key: WFLY-7508 URL: https://issues.jboss.org/browse/WFLY-7508 Project: WildFly Issue Type: Bug Components: EE Reporter: James Perkins Tasks submitted via a managed executor service continue running after an undeploy. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7276) EE Concurrency tasks continue running after a deployment has been removed

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-7276?page=com.atlassian.jira.plugin.... ] James Perkins reassigned WFLY-7276: ----------------------------------- Assignee: (was: James Perkins) > EE Concurrency tasks continue running after a deployment has been removed > ------------------------------------------------------------------------- > > Key: WFLY-7276 > URL: https://issues.jboss.org/browse/WFLY-7276 > Project: WildFly > Issue Type: Bug > Components: EE > Reporter: James Perkins > > Tasks submitted via a managed executor service continue running after an undeploy. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1950) Get rid of system property for turning off 'strict' transformers rejection testing

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1950?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-1950: ------------------------------- Description: WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release with WFCORE-1892. (was: WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release wit WFCORE-1892.) > Get rid of system property for turning off 'strict' transformers rejection testing > ---------------------------------------------------------------------------------- > > Key: WFCORE-1950 > URL: https://issues.jboss.org/browse/WFCORE-1950 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha12 > > > WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release with WFCORE-1892. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1950) Get rid of system property for turning off 'strict' transformers rejection testing

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1950?page=com.atlassian.jira.plugi... ] Kabir Khan updated WFCORE-1950: ------------------------------- Description: WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release wit WFCORE-1892. (was: WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. ) > Get rid of system property for turning off 'strict' transformers rejection testing > ---------------------------------------------------------------------------------- > > Key: WFCORE-1950 > URL: https://issues.jboss.org/browse/WFCORE-1950 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha12 > > > WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release wit WFCORE-1892. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7506) Get rid of usage of -Dwildfly.test.temp.disable.strict.check in ejb3 transformers tests

by Kabir Khan (JIRA)

Kabir Khan created WFLY-7506: -------------------------------- Summary: Get rid of usage of -Dwildfly.test.temp.disable.strict.check in ejb3 transformers tests Key: WFLY-7506 URL: https://issues.jboss.org/browse/WFLY-7506 Project: WildFly Issue Type: Bug Reporter: Kabir Khan Assignee: Kabir Khan See https://issues.jboss.org/browse/WFCORE-1950 for explanation. EJB3 needs reworking for this to work properly, and as an interim solution uses the system property. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7507) Get rid of usage of -Dwildfly.test.temp.disable.strict.check in ejb3 transformers tests

by Kabir Khan (JIRA)

Kabir Khan created WFLY-7507: -------------------------------- Summary: Get rid of usage of -Dwildfly.test.temp.disable.strict.check in ejb3 transformers tests Key: WFLY-7507 URL: https://issues.jboss.org/browse/WFLY-7507 Project: WildFly Issue Type: Bug Reporter: Kabir Khan Assignee: Kabir Khan See https://issues.jboss.org/browse/WFCORE-1950 for explanation. EJB3 needs reworking for this to work properly, and as an interim solution uses the system property. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016