October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-694) CLIENT-CERT mechanism is incorrectly called CLIENT_CERT

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-694?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-694: --------------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/525, https://github.com/wildfly-security/elytron-web/pull/40 (was: https://github.com/wildfly-security/wildfly-elytron/pull/525) > CLIENT-CERT mechanism is incorrectly called CLIENT_CERT > ------------------------------------------------------- > > Key: ELY-694 > URL: https://issues.jboss.org/browse/ELY-694 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta12 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1347) Explicit expiration of event not effective - regression from 6.4 to 6.5

by Thibault Daoulas (JIRA)

Thibault Daoulas created DROOLS-1347: ---------------------------------------- Summary: Explicit expiration of event not effective - regression from 6.4 to 6.5 Key: DROOLS-1347 URL: https://issues.jboss.org/browse/DROOLS-1347 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 6.5.0.Final Reporter: Thibault Daoulas Assignee: Mario Fusco I just ugraded my project from Drools 6.4.0.Final to 6.5.0.Final and have now quite a few tests on rules that fail, all have in common that they test the expiration of events, where an event that should have been removed from the working memory is still present. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ] Kabir Khan reassigned WFLY-6854: -------------------------------- Assignee: Scott Marlow (was: Kabir Khan) > 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.2#72004)

9 years, 6 months

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6854?page=com.atlassian.jira.plugin.... ] Kabir Khan reassigned WFLY-6854: -------------------------------- Assignee: Kabir Khan (was: Scott Marlow) > 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: Kabir Khan > 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.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-649) Make the exists and create methods on HttpScope default

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-649?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-649. ---------------------------------- Fix Version/s: 1.1.0.Beta10 (was: 1.1.0.Beta12) Resolution: Done > Make the exists and create methods on HttpScope default > ------------------------------------------------------- > > Key: ELY-649 > URL: https://issues.jboss.org/browse/ELY-649 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta10 > > -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7404) Upgrade Generic JMS RA to 2.0.0.Alpha1

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-7404?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-6697 to WFLY-7404: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7404 (was: JBEAP-6697) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) > Upgrade Generic JMS RA to 2.0.0.Alpha1 > -------------------------------------- > > Key: WFLY-7404 > URL: https://issues.jboss.org/browse/WFLY-7404 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > Upgrade Generic JMS RA to 2.0.0.Alpha1 to support JMS 2.0. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise edited comment on WFLY-7398 at 10/28/16 5:18 AM: ---------------------------------------------------------------------- It would also help to have a dump of the services valueType: ./static-provider=test:read-operation-description(name=add was (Author: jdenise): It would also help to have a dump of the services valueType: ./static-provider=test::read-operation-description(name=add > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise commented on WFLY-7398: -------------------------------------------- It would also help to have a dump of the services valueType: ./static-provider=test::read-operation-description(name=add > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7398) Tab completion causes NUL characters ('\0') to be injected...sometimes

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-7398?page=com.atlassian.jira.plugin.... ] Jean-Francois Denise commented on WFLY-7398: -------------------------------------------- David, is completion proposing you something for the uri property value? It would help to know the completion sequence. I guess that the services argument is ruled by a value type and the completion adds automatically for you =[{ Then you are proposed a the list of properties of services, you type part of uri, then TAB "=" is added automatically then you press TAB multiple time (twice it seems). Is that the steps you have followed? Thanks. JF > Tab completion causes NUL characters ('\0') to be injected...sometimes > ---------------------------------------------------------------------- > > Key: WFLY-7398 > URL: https://issues.jboss.org/browse/WFLY-7398 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: David Lloyd > Assignee: Jean-Francois Denise > Priority: Critical > > I noticed while testing my subsystem that sometimes using tab-complete on an attribute causes NUL ('\0') characters to be injected into the input. These characters are invisible on the screen but cause XML marshalling to fail as that character is forbidden. > My "less" output of .jboss-cli-history looks something like this: > {noformat} > embed-server --std-out=echo > cd subsystem=discovery > ./static-provider=test:add(services=[{uri=^@^@"local", abstract-type="ejb", abstract-type-authority="jboss"}]) > ./static-provider=test4:add(services=[{uri="local", abstract-type="ejb", abstract-type-authority="jboss"}]) > {noformat} > In the first "test:add" case I used tab-completion; in the second "test4:add" case I typed it out by hand. The "^@" are in inverse video in less, indicating a NUL character. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1407) Test coverage for syslog reconnection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1407?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated WFCORE-1407: -------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1311440 Bugzilla Update: Perform > Test coverage for syslog reconnection > ------------------------------------- > > Key: WFCORE-1407 > URL: https://issues.jboss.org/browse/WFCORE-1407 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 2.1.0.CR2 > Reporter: Ondrej Lukas > Assignee: Ondrej Lukas > Fix For: 3.0.0.Alpha1 > > > Added test coverage for syslog reconnection issues - https://issues.jboss.org/browse/LOGMGR-123. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 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 October 2016