February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3505) Booting a domain slave with no cached domain.xml and no available master does not exit as expected

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3505?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3505: ---------------------------------- Fix Version/s: 4.0.0.Alpha6 > Booting a domain slave with no cached domain.xml and no available master does not exit as expected > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-3505 > URL: https://issues.jboss.org/browse/WFCORE-3505 > Project: WildFly Core > Issue Type: Bug > Reporter: Ken Wills > Assignee: Ken Wills > Fix For: 4.0.0.Alpha6 > > > As part of the empty config HC work, 0 length configurations were considered to be "empty". This is not correct in the case of domain.xml and a slave using --cached-dc if the master is unavailable on initial boot. > Since the embedded empty config is always using supressLoad with --empty-domain-config, zero length domain.xml / domain-cached.xml is an error, and result in an exception and exit. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3575) CLI, failed connect side effect

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3575?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3575: ---------------------------------- Fix Version/s: 4.0.0.Beta1 > CLI, failed connect side effect > ------------------------------- > > Key: WFCORE-3575 > URL: https://issues.jboss.org/browse/WFCORE-3575 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Priority: Blocker > Fix For: 4.0.0.Beta1 > > > An attempt to connect that fails makes the current context unusable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9823) Servlet 4 API 1.0.0.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9823: ------------------------------------ Summary: Servlet 4 API 1.0.0.Final Key: WFLY-9823 URL: https://issues.jboss.org/browse/WFLY-9823 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9822) JBoss metadata 11.0.0.Final

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9822: ------------------------------------ Summary: JBoss metadata 11.0.0.Final Key: WFLY-9822 URL: https://issues.jboss.org/browse/WFLY-9822 Project: WildFly Issue Type: Component Upgrade Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3447) CLI SSL security commands.

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3447?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3447: ---------------------------------- Fix Version/s: 4.0.0.Beta1 > CLI SSL security commands. > -------------------------- > > Key: WFCORE-3447 > URL: https://issues.jboss.org/browse/WFCORE-3447 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > Fix For: 4.0.0.Beta1 > > > In order to help configure SSL server side security, a set of CLI commands should be defined to drive users to realise the main use cases: > - enable / disable SSL for management interfaces > - enable / disable SSL for web server. > These commands rely on the new elytron operations to manage key-store. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3600) JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file, seems that Elytron uses JSON-P stuff too early

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3600?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3600: ---------------------------------- Fix Version/s: 4.0.0.Beta1 > JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file, seems that Elytron uses JSON-P stuff too early > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3600 > URL: https://issues.jboss.org/browse/WFCORE-3600 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Rostislav Svoboda > Assignee: James Perkins > Priority: Critical > Fix For: 4.0.0.Beta1 > > > JSON-P 1.1 is not loaded when ee8.preview.mode property is defined in standalone.xml file. > Early investigation done by James and Stuart indicates that Elytron uses JSON-P stuff too early and it prevents JSON-P 1.1 activation when ee8.preview.mode property is defined in standalone.xml file. > CCing [~jamezp] [~swd847] [~jason.greene] [~kabirkhan] [~brian.stansberry] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9628) Bean Validation 2.0 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9628?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9628: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/10725, https://github.com/wildfly/wildfly/pull/10875 (was: https://github.com/wildfly/wildfly/pull/10725) > Bean Validation 2.0 Support > --------------------------- > > Key: WFLY-9628 > URL: https://issues.jboss.org/browse/WFLY-9628 > Project: WildFly > Issue Type: Sub-task > Reporter: Gunnar Morling > Assignee: Guillaume Smet > > WildFly proposal: https://github.com/wildfly/wildfly-proposals/pull/17 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9757) Some jsf integration tests fail if -Dnode != localhost

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-9757?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFLY-9757: ---------------------------------- {{DoctypeDeclTestCase#testDoctypeDeclDisallowed}} currently attempts to check that the HTTP response contains a specific error message from the stack trace when attempting to access a JSF application that contains a DOCTYPE declaration. However, when WildFly is bound to an IP address other than localhost, attempting to access a JSF application that contains a DOCTYPE declaration will result in an Internal Server Error, as expected, but the stack trace containing the error message won't be part of the HTTP response as it is when WildFly is bound to localhost. The test should be updated to just make sure an Internal Server Error occurs instead of also checking that the response string contains the error message from the stack trace. > Some jsf integration tests fail if -Dnode != localhost > ------------------------------------------------------ > > Key: WFLY-9757 > URL: https://issues.jboss.org/browse/WFLY-9757 > Project: WildFly > Issue Type: Bug > Components: JSF, Test Suite > Reporter: Petr Kremensky > Assignee: Farah Juma > Attachments: org.jboss.as.test.integration.jsf.doctype.DoctypeDeclTestCase-output.txt > > > Running the tests keeping a node0 to localhost works fine: > {noformat} > [pkremens@localhost testsuite] (master)$ mvn test -Dts.basic -Dts.noSmoke -Dtest=DoctypeDeclTestCase,DuplicateIDIntegrationTestCase,InjectionToPhaseListenerTest > ... > Running org.jboss.as.test.integration.jsf.doctype.DoctypeDeclTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.809 sec - in org.jboss.as.test.integration.jsf.doctype.DoctypeDeclTestCase > Running org.jboss.as.test.integration.jsf.duplicateid.DuplicateIDIntegrationTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.645 sec - in org.jboss.as.test.integration.jsf.duplicateid.DuplicateIDIntegrationTestCase > Running org.jboss.as.test.integration.jsf.phaseListener.injectionTarget.InjectionToPhaseListenerTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.1 sec - in org.jboss.as.test.integration.jsf.phaseListener.injectionTarget.InjectionToPhaseListenerTest > {noformat} > But once node0 is set, the tests start to fail. > {noformat} > [pkremens@localhost testsuite] (master)$ mvn test -Dts.basic -Dts.noSmoke -Dtest=DoctypeDeclTestCase,DuplicateIDIntegrationTestCase,InjectionToPhaseListenerTest -Dnode0=<IP> > ... > Failed tests: > DoctypeDeclTestCase.testDoctypeDeclDisallowed:93 > DuplicateIDIntegrationTestCase.testDuplicateIDIsNotGenerated:107 expected:<200> but was:<500> > Tests in error: > InjectionToPhaseListenerTest.test:61 » IO java.util.concurrent.ExecutionExcept... > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5459) Rename JGroups-related attributes

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-5459?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-5459: ---------------------------------- Assignee: Paul Ferraro (was: Jeff Mesnil) > Rename JGroups-related attributes > --------------------------------- > > Key: WFLY-5459 > URL: https://issues.jboss.org/browse/WFLY-5459 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR2 > Reporter: Jeff Mesnil > Assignee: Paul Ferraro > > Based on Paul feedback in https://github.com/wildfly/wildfly/pull/8221#issuecomment-145013596: > {quote}You may want to consider renaming these attributes, however, since the names are now a little confusing. For example, jgroups-stack is perhaps better described as jgroups-channel-factory, since it can specify either a stack name or a channel name. jgroups-channel is also confusing in this context, since this specifies either the cluster name, in the case where jgroups-stack specifies a stack; or the fork name, in the case where the jgroups-stack specifies a channel name. Perhaps jgroups-cluster-name is a better choice?{quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7185) JSON-B 1.0 Support

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-7185?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-7185: ------------------------------------- Analysis documentation https://github.com/wildfly/wildfly-proposals/pull/22. > JSON-B 1.0 Support > ------------------ > > Key: WFLY-7185 > URL: https://issues.jboss.org/browse/WFLY-7185 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: James Perkins > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 February 2018