October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7378) HTTP/2 is still enabled even if JCE is not installed

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7378?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-7378: --------------------------------- Component/s: Web (Undertow) > HTTP/2 is still enabled even if JCE is not installed > ---------------------------------------------------- > > Key: WFLY-7378 > URL: https://issues.jboss.org/browse/WFLY-7378 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Jason Greene > > This results in connection errors when using h2 as no strong ciphers are installed -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7378) HTTP/2 is still enabled even if JCE is not installed

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7378?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-7378: ------------------------------------ Assignee: Stuart Douglas (was: Jason Greene) > HTTP/2 is still enabled even if JCE is not installed > ---------------------------------------------------- > > Key: WFLY-7378 > URL: https://issues.jboss.org/browse/WFLY-7378 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > This results in connection errors when using h2 as no strong ciphers are installed -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7376) The ServletResourceManager hard codes the safe symlink paths as '/'

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-7376: ------------------------------------ Summary: The ServletResourceManager hard codes the safe symlink paths as '/' Key: WFLY-7376 URL: https://issues.jboss.org/browse/WFLY-7376 Project: WildFly Issue Type: Bug Reporter: Stuart Douglas Assignee: Jason Greene This causes problems on windows -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7377) The ServletResourceManager hard codes the safe symlink paths as '/'

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-7377: ------------------------------------ Summary: The ServletResourceManager hard codes the safe symlink paths as '/' Key: WFLY-7377 URL: https://issues.jboss.org/browse/WFLY-7377 Project: WildFly Issue Type: Bug Reporter: Stuart Douglas Assignee: Jason Greene This causes problems on windows -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7377) The ServletResourceManager hard codes the safe symlink paths as '/'

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7377?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-7377: ------------------------------------ Component/s: Web (Undertow) Assignee: Stuart Douglas (was: Jason Greene) > The ServletResourceManager hard codes the safe symlink paths as '/' > ------------------------------------------------------------------- > > Key: WFLY-7377 > URL: https://issues.jboss.org/browse/WFLY-7377 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > This causes problems on windows -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7376) The ServletResourceManager hard codes the safe symlink paths as '/'

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7376?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-7376: ------------------------------------ Component/s: Web (Undertow) Assignee: Stuart Douglas (was: Jason Greene) > The ServletResourceManager hard codes the safe symlink paths as '/' > ------------------------------------------------------------------- > > Key: WFLY-7376 > URL: https://issues.jboss.org/browse/WFLY-7376 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > > This causes problems on windows -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7367) add per PU cache of the new temp classloader returned from PersistenceUnitMetadataImpl.getNewTempClassLoader()

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-7367?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-7367: ------------------------------------ [https://java.net/projects/jpa-spec/lists/users/archive/2016-10/message/1] proposes a change to allow the new temp classloader to be cached per persistence unit (for the scope of the createContainerEntityManagerFactory() call). > add per PU cache of the new temp classloader returned from PersistenceUnitMetadataImpl.getNewTempClassLoader() > -------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7367 > URL: https://issues.jboss.org/browse/WFLY-7367 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > > The new temporary classloader returned by the WildFly PersistenceUnitInfo.getNewTempClassLoader() is currently created on every call. > Ensure that the cached temp classloader reference is cleared after the PersistenceProvider.createContainerEntityManagerFactory() call returns. > Javadoc description from [http://docs.oracle.com/javaee/7/api/javax/persistence/spi/PersistenceUnit...] > {quote} > ClassLoader getNewTempClassLoader() > Return a new instance of a ClassLoader that the provider may use to temporarily load any classes, resources, or open URLs. The scope and classpath of this loader is exactly the same as that of the loader returned by getClassLoader(). None of the classes loaded by this class loader will be visible to application components. The provider may only use this ClassLoader within the scope of the PersistenceProvider.createContainerEntityManagerFactory(javax.persistence.spi.PersistenceUnitInfo, java.util.Map) call. > Returns: > temporary ClassLoader with same visibility as current loader > {quote} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1868) wrong parse of double quote in `\\"`

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1868?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-1868: ---------------------------------------------- Hi Hisanobu, I have commented on your PR saying that we had understood the issue and that I was Ok with this fix being merged. Regards. JF > wrong parse of double quote in `\\"` > ------------------------------------- > > Key: WFCORE-1868 > URL: https://issues.jboss.org/browse/WFCORE-1868 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: JBoss EAP 7.0.0 > Reporter: Hisanobu Okuda > Assignee: Jean-Francois Denise > > jboss-cli does not parse command line if command line contains {code}\\"{code} > When a command is > {code}/system-property=foo4:add(value="vvv\\"){code} > it shows the sub-prompt '> ' like: > {code} > [standalone@localhost:9990 /] /system-property=foo4:add(value="vvv\\") > > > {code} -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7375) Upgrade Netty to 4.0.42.FINAL

by Tobias Stadler (JIRA)

Tobias Stadler created WFLY-7375: ------------------------------------ Summary: Upgrade Netty to 4.0.42.FINAL Key: WFLY-7375 URL: https://issues.jboss.org/browse/WFLY-7375 Project: WildFly Issue Type: Component Upgrade Components: JMS Affects Versions: 10.1.0.Final Reporter: Tobias Stadler Assignee: Jeff Mesnil Upgrade Netty to 4.0.42.FINAL, -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-790) CLI Does Not Log History With "--file" and "--command(s)" args

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-790?page=com.atlassian.jira.plugin... ] Jean-Francois Denise commented on WFCORE-790: --------------------------------------------- Whatever the Aesh/CLI design issue, I think that history means interactive. If we want it for non interactive, a user should have to tweak his script to enable it. We could imagine that a script containing the command history --enable would force the history to be updated. > CLI Does Not Log History With "--file" and "--command(s)" args > --------------------------------------------------------------- > > Key: WFCORE-790 > URL: https://issues.jboss.org/browse/WFCORE-790 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Affects Versions: 2.0.0.Alpha5 > Reporter: Petr Kremensky > Assignee: Jean-Francois Denise > > Cli doesn't log commands passed by "\-\-file" and "\-\-command(s)" arguments. > https://bugzilla.redhat.com/show_bug.cgi?id=1232890 -- 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