September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9357) [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9357?page=com.atlassian.jira.plugin.... ] Jason Greene moved JBEAP-13185 to WFLY-9357: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9357 (was: JBEAP-13185) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB Naming (was: EJB) (was: Naming) > [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9357 > URL: https://issues.jboss.org/browse/WFLY-9357 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Environment: 7.1.0.Beta and 7.1.0.ER2 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Final > > > It is expected that the user can be overridden witht he properties passed to InitialContext. > But the user logged at the server side is still the one from the wildfy-config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9357) [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9357?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9357: ------------------------------- Steps to Reproduce: (was: User project https://github.com/wfink/jboss-eap7.1-playground and check https://github.com/wfink/jboss-eap7.1-playground/blob/master/clients/Wild...) > [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9357 > URL: https://issues.jboss.org/browse/WFLY-9357 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Environment: 7.1.0.Beta and 7.1.0.ER2 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Final > > > It is expected that the user can be overridden witht he properties passed to InitialContext. > But the user logged at the server side is still the one from the wildfy-config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9357) [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9357?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9357: ------------------------------- Environment: WildFly 11 CR1 (was: 7.1.0.Beta and 7.1.0.ER2) > [GSS](7.1.0) User can not overridden with InitialContext properties as expected if wilfdfly-config-xml is used > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9357 > URL: https://issues.jboss.org/browse/WFLY-9357 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Environment: WildFly 11 CR1 > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Blocker > Fix For: 11.0.0.Final > > > It is expected that the user can be overridden witht he properties passed to InitialContext. > But the user logged at the server side is still the one from the wildfy-config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-31) Enforce DataSource.close()

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-31?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-31. ----------------------------- Resolution: Done > Enforce DataSource.close() > -------------------------- > > Key: AG-31 > URL: https://issues.jboss.org/browse/AG-31 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.3 > > > Make sure that no connections are handled after the DataSource is closed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-31) Enforce DataSource.close()

by Luis Barreiro (JIRA)

Luis Barreiro created AG-31: ------------------------------- Summary: Enforce DataSource.close() Key: AG-31 URL: https://issues.jboss.org/browse/AG-31 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 0.2 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.3 Make sure that no connections are handled after the DataSource is closed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-30) Update Junit to 5..0.0

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-30?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-30. ----------------------------- Resolution: Done > Update Junit to 5..0.0 > ---------------------- > > Key: AG-30 > URL: https://issues.jboss.org/browse/AG-30 > Project: Agroal > Issue Type: Bug > Components: build > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-30) Update Junit to 5..0.0

by Luis Barreiro (JIRA)

Luis Barreiro created AG-30: ------------------------------- Summary: Update Junit to 5..0.0 Key: AG-30 URL: https://issues.jboss.org/browse/AG-30 Project: Agroal Issue Type: Bug Components: build Affects Versions: 0.2 Reporter: Luis Barreiro Assignee: Luis Barreiro Priority: Minor Fix For: 0.3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-28) Add other sources to AgroalPropertiesReader

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-28?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-28. ----------------------------- Resolution: Done > Add other sources to AgroalPropertiesReader > ------------------------------------------- > > Key: AG-28 > URL: https://issues.jboss.org/browse/AG-28 > Project: Agroal > Issue Type: Bug > Components: api > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.3 > > > Expose reading from Map<String, String>, Properties, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-29) Security not set when Driver class is not specified

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-29?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-29. ----------------------------- Resolution: Done > Security not set when Driver class is not specified > --------------------------------------------------- > > Key: AG-29 > URL: https://issues.jboss.org/browse/AG-29 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.2 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.3 > > > When Driver is load through DriverManager, the user / password properties are not set -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3304) PathInfoHandler should use a parseable format for its timestamps

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3304?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3304: ------------------------------------- Description: [~jamezp] said on https://github.com/wildfly/wildfly-core/pull/2730: we should probably use something like `DateTimeFormatter.ISO_OFFSET_DATE_TIME` so it's a standard format that could be parsed. Current format: {code} 2017-09-18T22:48:24.367ZAmerica/Los_Angeles {code} DateTimeFormatter.ISO_OFFSET_DATE_TIME {code} 2017-09-18T15:48:24.367-07:00 {code} I guess another option is DateTimeFormatter.ISO_ZONED_DATE_TIME which would be {code} 2017-09-18T15:56:21.875-07:00[America/Los_Angeles] {code} was: [~jamezp] said on https://github.com/wildfly/wildfly-core/pull/2730: we should probably use something like `DateTimeFormatter.ISO_OFFSET_DATE_TIME` so it's a standard format that could be parsed. Current format: {code} 2017-09-18T22:48:24.367ZAmerica/Los_Angeles {code} DateTimeFormatter.ISO_OFFSET_DATE_TIME {code} 2017-09-18T15:48:24.367-07:00 {code} > PathInfoHandler should use a parseable format for its timestamps > ---------------------------------------------------------------- > > Key: WFCORE-3304 > URL: https://issues.jboss.org/browse/WFCORE-3304 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Assignee: ehsavoie Hugonnet > > [~jamezp] said on https://github.com/wildfly/wildfly-core/pull/2730: > we should probably use something like `DateTimeFormatter.ISO_OFFSET_DATE_TIME` so it's a standard format that could be parsed. > Current format: > {code} > 2017-09-18T22:48:24.367ZAmerica/Los_Angeles > {code} > DateTimeFormatter.ISO_OFFSET_DATE_TIME > {code} > 2017-09-18T15:48:24.367-07:00 > {code} > I guess another option is DateTimeFormatter.ISO_ZONED_DATE_TIME which would be > {code} > 2017-09-18T15:56:21.875-07:00[America/Los_Angeles] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017