July 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6840) Tab completion does not work in message-activemq subsystem for "path" attributes

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6840?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-5237 to WFLY-6840: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-6840 (was: JBEAP-5237) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) Affects Version/s: 10.0.0.Final (was: 7.0.0.GA) > Tab completion does not work in message-activemq subsystem for "path" attributes > --------------------------------------------------------------------------------- > > Key: WFLY-6840 > URL: https://issues.jboss.org/browse/WFLY-6840 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > Tab completion does not work in message-activemq subsystem for "path" attributes. For example when trying to specify exported journal file on file system for {{:import-journal}} operation: > {code} > /subsystem=messaging-activemq/server=default:import-journal(file=/home/mnovak/jour <-- tab does not provide help > {code} > Pressing Tab does not provide help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6840) Tab completion does not work in messaging-activemq subsystem for "path" attributes

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6840?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-6840: ------------------------------ Summary: Tab completion does not work in messaging-activemq subsystem for "path" attributes (was: Tab completion does not work in message-activemq subsystem for "path" attributes ) > Tab completion does not work in messaging-activemq subsystem for "path" attributes > ----------------------------------------------------------------------------------- > > Key: WFLY-6840 > URL: https://issues.jboss.org/browse/WFLY-6840 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > Tab completion does not work in message-activemq subsystem for "path" attributes. For example when trying to specify exported journal file on file system for {{:import-journal}} operation: > {code} > /subsystem=messaging-activemq/server=default:import-journal(file=/home/mnovak/jour <-- tab does not provide help > {code} > Pressing Tab does not provide help. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6784) Add possibility to enable websocket compression via management model

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-6784?page=com.atlassian.jira.plugin.... ] Carlo de Wolf updated WFLY-6784: -------------------------------- Labels: downstream_dependency (was: ) > Add possibility to enable websocket compression via management model > -------------------------------------------------------------------- > > Key: WFLY-6784 > URL: https://issues.jboss.org/browse/WFLY-6784 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Radim Hatlapatka > Assignee: Ingo Weiss > Priority: Critical > Labels: downstream_dependency > Original Estimate: 2 days > Time Spent: 2 days > Remaining Estimate: 0 minutes > > In EAP 6 the websockets compression was enabled by default allowing to use pre-deflate compression when requested by client. > There is support for it in Undertow but there is no option to enable it in WildFly 10. This option should be added to WildFly and should probably set by default to true as that would be consistent with default behaviour when using WebSockets with EAP 6.4. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6834) Store license files in repository

by Petr Sakař (JIRA)

[ https://issues.jboss.org/browse/WFLY-6834?page=com.atlassian.jira.plugin.... ] Petr Sakař commented on WFLY-6834: ---------------------------------- Please note that from the moment the PR is merged if anybody changes feature-pack/src/license/licenses.xml she/he has to change the content of feature-pack/src/main/resources/content/docs/licenses/ accordingly - copy there new licenses.xml and license (if not already there). Manually activated profile download-licenses can be used to do it > Store license files in repository > --------------------------------- > > Key: WFLY-6834 > URL: https://issues.jboss.org/browse/WFLY-6834 > Project: WildFly > Issue Type: Enhancement > Components: Build System > Reporter: Petr Sakař > Assignee: Petr Sakař > > store license files in the repository so the build copies the files to the distribution zip instead of downloading them. > Downloading at build time results in unpredictable errors and missing licenses when location of license is changed by project or url results in redirect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6839) It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-6839?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-6839: ------------------------------- Description: In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. {code} <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> ... ... <ValidatingAlias Key="localhost" Value="servercert" /> <ValidatingAlias Key="127.0.0.1" Value="servercert" /> </KeyProvider> {code} But in subsystem configuration I cannot do this. Workaround You can clone your certificate in keystore under different alias and then add new validating alias with this value. was: In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. {code} <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> ... ... <ValidatingAlias Key="localhost" Value="servercert" /> <ValidatingAlias Key="127.0.0.1" Value="servercert" /> </KeyProvider> {code} But in subsystem configuration I cannot do this. > It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6839 > URL: https://issues.jboss.org/browse/WFLY-6839 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Hynek Švábek > Assignee: Alexey Loubyansky > > In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. > {code} > <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> > ... > ... > <ValidatingAlias Key="localhost" Value="servercert" /> > <ValidatingAlias Key="127.0.0.1" Value="servercert" /> > </KeyProvider> > {code} > But in subsystem configuration I cannot do this. > Workaround > You can clone your certificate in keystore under different alias and then add new validating alias with this value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6839) It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml

by Hynek Švábek (JIRA)

[ https://issues.jboss.org/browse/WFLY-6839?page=com.atlassian.jira.plugin.... ] Hynek Švábek updated WFLY-6839: ------------------------------- Description: In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. {code} <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> ... ... <ValidatingAlias Key="localhost" Value="servercert" /> <ValidatingAlias Key="127.0.0.1" Value="servercert" /> </KeyProvider> {code} But in subsystem configuration I cannot do this. *Workaround* You can clone your certificate in keystore under different alias and then add new validating alias with this value. was: In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. {code} <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> ... ... <ValidatingAlias Key="localhost" Value="servercert" /> <ValidatingAlias Key="127.0.0.1" Value="servercert" /> </KeyProvider> {code} But in subsystem configuration I cannot do this. Workaround You can clone your certificate in keystore under different alias and then add new validating alias with this value. > It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-6839 > URL: https://issues.jboss.org/browse/WFLY-6839 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: Hynek Švábek > Assignee: Alexey Loubyansky > > In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. > {code} > <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> > ... > ... > <ValidatingAlias Key="localhost" Value="servercert" /> > <ValidatingAlias Key="127.0.0.1" Value="servercert" /> > </KeyProvider> > {code} > But in subsystem configuration I cannot do this. > *Workaround* > You can clone your certificate in keystore under different alias and then add new validating alias with this value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) javassist should also be exported to Hibernate (native) applications

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Carlo de Wolf updated WFLY-459: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/8474 (was: https://github.com/jbossas/jboss-as/pull/2766) > javassist should also be exported to Hibernate (native) applications > -------------------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Blocker > Labels: downstream_dependency > Fix For: 10.1.0.Final > > > Originally this jira was to stop exporting the javassist module to JPA deployments but it turns out that is fine to do. In addition, native Hibernate applications that depend on Hibernate, should also get the javassist dependency. > # native Hibernate applications will get the javassist dependency via the application dependency on org.hibernate. > # container managed JPA applications will get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). > # container managed JPA applications that embed their own copy of Hibernate jars will also get the javassist dependency via org.jboss.as.jpa.processor.JPADependencyProcessor (JPA deployer). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1654) Enhancements for set/unset test suite

by Martin Schvarcbacher (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1654?page=com.atlassian.jira.plugi... ] Martin Schvarcbacher updated WFCORE-1654: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1681 > Enhancements for set/unset test suite > ------------------------------------- > > Key: WFCORE-1654 > URL: https://issues.jboss.org/browse/WFCORE-1654 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Reporter: Martin Schvarcbacher > Assignee: Martin Schvarcbacher > Priority: Minor > > Added tests for jboss-cli ‘set’ and ‘unset’ commands > Use cases: > set variable1=value > set variable2=$variable1 > unset variable1 > set #prints all set variables -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6620) Remove typo from BAControler interface and its implementations

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-6620?page=com.atlassian.jira.plugin.... ] Gytis Trikleris resolved WFLY-6620. ----------------------------------- Resolution: Done Yes sorry. It was resolved by https://github.com/wildfly/wildfly/pull/8817. > Remove typo from BAControler interface and its implementations > -------------------------------------------------------------- > > Key: WFLY-6620 > URL: https://issues.jboss.org/browse/WFLY-6620 > Project: WildFly > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6839) It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml

by Hynek Švábek (JIRA)

Hynek Švábek created WFLY-6839: ---------------------------------- Summary: It is impossible configure KeyStore ValidatingAlias in picketlink-federation subsystem same as in picketlink.xml Key: WFLY-6839 URL: https://issues.jboss.org/browse/WFLY-6839 Project: WildFly Issue Type: Bug Components: CLI Reporter: Hynek Švábek Assignee: Alexey Loubyansky In picketlink.xml configuration file I can define multiple ValidatingAlias for same certificate alias. {code} <KeyProvider ClassName="org.picketlink.identity.federation.core.impl.KeyStoreKeyManager"> ... ... <ValidatingAlias Key="localhost" Value="servercert" /> <ValidatingAlias Key="127.0.0.1" Value="servercert" /> </KeyProvider> {code} But in subsystem configuration I cannot do this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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