February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9866) (EE8 mode of) module javax.faces.api needs a dependency on javax.websocket.api

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9866?page=com.atlassian.jira.plugin.... ] Scott Marlow reassigned WFLY-9866: ---------------------------------- Assignee: Scott Marlow (was: Jason Greene) > (EE8 mode of) module javax.faces.api needs a dependency on javax.websocket.api > ------------------------------------------------------------------------------ > > Key: WFLY-9866 > URL: https://issues.jboss.org/browse/WFLY-9866 > Project: WildFly > Issue Type: Task > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.CR1 > > > Noticed during EE 8 testing, that javax.faces.event.WebsocketEvent needs a dependency on javax.websocket.CloseReason, so we probably need something like: > {code} > <module name="javax.faces.api" xmlns="urn:jboss:module:1.7"> > <dependencies> > <module name="com.sun.jsf-impl"/> > <module name="javax.enterprise.api" export="true"/> > <module name="javax.servlet.api" export="true"/> > <module name="javax.servlet.jsp.api" export="true"/> > <module name="javax.servlet.jstl.api" export="true"/> > <module name="javax.validation.api" export="true"/> > <module name="org.glassfish.javax.el" export="true"/> > <module name="javax.api"/> > <module name="javax.websocket.api"/> > </dependencies> > <resources> > <resource-root path="jboss-jsf-api_2.2_spec-2.2.14.jar"> > <conditions> > <property-not-equal name="ee8.preview.mode" value="true"/> > </conditions> > </resource-root> > <resource-root path="jboss-jsf-api_2.3_spec-2.3.3.SP1.jar"> > <conditions> > <property-equal name="ee8.preview.mode" value="true"/> > </conditions> > </resource-root> > </resources> > </module> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9866) (EE8 mode of) module javax.faces.api needs a dependency on javax.websocket.api

by Scott Marlow (JIRA)

Scott Marlow created WFLY-9866: ---------------------------------- Summary: (EE8 mode of) module javax.faces.api needs a dependency on javax.websocket.api Key: WFLY-9866 URL: https://issues.jboss.org/browse/WFLY-9866 Project: WildFly Issue Type: Task Reporter: Scott Marlow Assignee: Jason Greene Fix For: 12.0.0.CR1 Noticed during EE 8 testing, that javax.faces.event.WebsocketEvent needs a dependency on javax.websocket.CloseReason, so we probably need something like: {code} <module name="javax.faces.api" xmlns="urn:jboss:module:1.7"> <dependencies> <module name="com.sun.jsf-impl"/> <module name="javax.enterprise.api" export="true"/> <module name="javax.servlet.api" export="true"/> <module name="javax.servlet.jsp.api" export="true"/> <module name="javax.servlet.jstl.api" export="true"/> <module name="javax.validation.api" export="true"/> <module name="org.glassfish.javax.el" export="true"/> <module name="javax.api"/> <module name="javax.websocket.api"/> </dependencies> <resources> <resource-root path="jboss-jsf-api_2.2_spec-2.2.14.jar"> <conditions> <property-not-equal name="ee8.preview.mode" value="true"/> </conditions> </resource-root> <resource-root path="jboss-jsf-api_2.3_spec-2.3.3.SP1.jar"> <conditions> <property-equal name="ee8.preview.mode" value="true"/> </conditions> </resource-root> </resources> </module> {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3625) Elytron subsystem template does not match what we persist

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3625?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3625: ---------------------------------------- Assignee: (was: Brian Stansberry) https://github.com/wildfly/wildfly-core/compare/master...bstansberry:WFCO... fixes the parser order to match the xsd, but it results in a lot of elytron subsystem test failures. It looks like a lot of the test xml files use the incorrect order. > Elytron subsystem template does not match what we persist > --------------------------------------------------------- > > Key: WFCORE-3625 > URL: https://issues.jboss.org/browse/WFCORE-3625 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Brian Stansberry > Fix For: 4.0.0.Beta2 > > > When we persist domain.xml in full, the elytron subsystem ends up being reordered vs what we shipped in the standard config. I assume this occurs with all the config files. > The element and attribute order in the standard config, the persistence and the xsd should be the same. > Specifically: > audit-logging moves from after providers to before > http moves from before sasl to after > The xsd agrees with what's in the standard config so this looks to be a marshalling problem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9865) Upgrade jastow to 2.0.3.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9865?page=com.atlassian.jira.plugin.... ] Ivo Studensky reassigned WFLY-9865: ----------------------------------- Assignee: Stuart Douglas (was: Petr Sakař) > Upgrade jastow to 2.0.3.Final > ----------------------------- > > Key: WFLY-9865 > URL: https://issues.jboss.org/browse/WFLY-9865 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Ivo Studensky > Assignee: Stuart Douglas > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9865) Upgrade jastow to 2.0.3.Final

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-9865?page=com.atlassian.jira.plugin.... ] Ivo Studensky moved JBEAP-14267 to WFLY-9865: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9865 (was: JBEAP-14267) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Web (Undertow) (was: Build System) Affects Version/s: (was: 7.0.8.GA) > Upgrade jastow to 2.0.3.Final > ----------------------------- > > Key: WFLY-9865 > URL: https://issues.jboss.org/browse/WFLY-9865 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Ivo Studensky > Assignee: Petr Sakař > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-32) Automate Installing Istio using Ansible

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-32: -------------------------------------------- Summary: Automate Installing Istio using Ansible Key: SWSQE-32 URL: https://issues.jboss.org/browse/SWSQE-32 Project: Swift Sunshine QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-32) Automate Installing Istio using Ansible

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-32?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo reassigned SWSQE-32: -------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Automate Installing Istio using Ansible > ---------------------------------------- > > Key: SWSQE-32 > URL: https://issues.jboss.org/browse/SWSQE-32 > Project: Swift Sunshine QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-1519) Make restore of SecurityIdentity on replicated session configurable

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1519?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1519: --------------------------------------- This cold possibly be simple achieved in the identity cache and check if the CachedIdentity does have a SecurityIdentity, if it doesn't just drop it. > Make restore of SecurityIdentity on replicated session configurable > ------------------------------------------------------------------- > > Key: ELY-1519 > URL: https://issues.jboss.org/browse/ELY-1519 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.2.0.Final > Reporter: Martin Choma > > Currently in clustered environment Security Identity is restored during > * failover > * load balancer change node (not sticky behaviour) > * session passivation/activation > This is mainly expected and good. It ensures performance gain because no additional SPNEGO negotiation is performed. But it can make troubles for kerberos ticket propagation, as kerberos ticket can't be serialized and restored. > So idea is to have flag to turn this default behaviour off. When user authenticate to app1 on serverA and then wants to access app1 on serverB, SPNEGO authentication will be activated and kerberos ticket will be negotiated and will be available on serverB as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-9) Select UI Automation Framework

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-9?page=com.atlassian.jira.plugin.sy... ] Matt Mahoney updated SWSQE-9: ----------------------------- Team: Infrastructure > Select UI Automation Framework > ------------------------------ > > Key: SWSQE-9 > URL: https://issues.jboss.org/browse/SWSQE-9 > Project: Swift Sunshine QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > > Team Infrastructure Task - *Team decision out framework selection* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6781) Wildfly cluster's failover functionality doesn't work as expected

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-6781?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-6781. ---------------------------- Resolution: Out of Date > Wildfly cluster's failover functionality doesn't work as expected > ----------------------------------------------------------------- > > Key: WFLY-6781 > URL: https://issues.jboss.org/browse/WFLY-6781 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.2.0.Final > Reporter: Preeta Kuruvilla > Assignee: Jeff Mesnil > Attachments: domain.Node1.xml, host.Node1.xml, host.Node2.xml, server.RC.Node1.AfterFailover.log, server.RC.Node1.BeforeFailover.log, server.RC.Node2.AfterFailover.log, server.RC.Node2.BeforeFailover.log, server.SL.Node1.AfterFailover.log, server.SL.Node1.BeforeFailover.log > > > Following are the testing scenarios we did and the outcome:- > 1. Network disabling on a VM for testing failover – Not working for both Linux and Windows environment. > 2. Power off of a VM using VMware client for testing failover – Is working on Linux environment but not working on windows environment. > 3. Ctrl + C method to stop services on a node for testing failover – works on both linux and windows environment > 4. Stopping server running on Node /VM using Admin Console for testing failover - works on both linux and windows environment. > Jgroups subsystem configuration in domain.xml we have is below:- > <subsystem xmlns="urn:jboss:domain:jgroups:2.0" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE2"/> > <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> -- 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