September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2879) Remove duplicated code from test cases where custom modules are needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2879?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2879: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1147391|https://bugzilla.redhat.com/show_bug.cgi?id=1147391] from NEW to ASSIGNED > Remove duplicated code from test cases where custom modules are needed > ---------------------------------------------------------------------- > > Key: WFLY-2879 > URL: https://issues.jboss.org/browse/WFLY-2879 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > When writing some integration tests for the PicketLink subsystem, I've noticed that there is no utility class or API to make easier create and remove custom modules from the modules directory. > There are a few tests with this requirement, and most of them are replicating code. > After discussing with [~kabirkhan], he suggested to open this JIRA to review those test cases and make them use a reusable component to work with custom modules. > I've already wrote a class that I think can satisfy all test cases requiring a custom module. > See https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration.... > Usage example: https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2879) Remove duplicated code from test cases where custom modules are needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2879?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2879: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147390, https://bugzilla.redhat.com/show_bug.cgi?id=1147391 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1147390) > Remove duplicated code from test cases where custom modules are needed > ---------------------------------------------------------------------- > > Key: WFLY-2879 > URL: https://issues.jboss.org/browse/WFLY-2879 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > When writing some integration tests for the PicketLink subsystem, I've noticed that there is no utility class or API to make easier create and remove custom modules from the modules directory. > There are a few tests with this requirement, and most of them are replicating code. > After discussing with [~kabirkhan], he suggested to open this JIRA to review those test cases and make them use a reusable component to work with custom modules. > I've already wrote a class that I think can satisfy all test cases requiring a custom module. > See https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration.... > Usage example: https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2879) Remove duplicated code from test cases where custom modules are needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2879?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2879: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1147390|https://bugzilla.redhat.com/show_bug.cgi?id=1147390] from NEW to ASSIGNED > Remove duplicated code from test cases where custom modules are needed > ---------------------------------------------------------------------- > > Key: WFLY-2879 > URL: https://issues.jboss.org/browse/WFLY-2879 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > When writing some integration tests for the PicketLink subsystem, I've noticed that there is no utility class or API to make easier create and remove custom modules from the modules directory. > There are a few tests with this requirement, and most of them are replicating code. > After discussing with [~kabirkhan], he suggested to open this JIRA to review those test cases and make them use a reusable component to work with custom modules. > I've already wrote a class that I think can satisfy all test cases requiring a custom module. > See https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration.... > Usage example: https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2879) Remove duplicated code from test cases where custom modules are needed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2879?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2879: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147390 > Remove duplicated code from test cases where custom modules are needed > ---------------------------------------------------------------------- > > Key: WFLY-2879 > URL: https://issues.jboss.org/browse/WFLY-2879 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 8.1.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > When writing some integration tests for the PicketLink subsystem, I've noticed that there is no utility class or API to make easier create and remove custom modules from the modules directory. > There are a few tests with this requirement, and most of them are replicating code. > After discussing with [~kabirkhan], he suggested to open this JIRA to review those test cases and make them use a reusable component to work with custom modules. > I've already wrote a class that I think can satisfy all test cases requiring a custom module. > See https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration.... > Usage example: https://github.com/pedroigor/wildfly/blob/WFLY-2733/testsuite/integration... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3910) To be added AJP connector connectionTimeout parameter

by Angel Ivanov (JIRA)

Angel Ivanov created WFLY-3910: ---------------------------------- Summary: To be added AJP connector connectionTimeout parameter Key: WFLY-3910 URL: https://issues.jboss.org/browse/WFLY-3910 Project: WildFly Issue Type: Feature Request Components: ConfigAdmin Affects Versions: 8.1.0.Final Reporter: Angel Ivanov Assignee: Thomas Diesler Hi, We need configuration parameter for Undertow to manage especially AJP connector connection timeout, because created threads staid alive forever. In tomcat such kind of connector parameter was connectionTimeout. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1851) RSVP: add option to not block caller

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1851?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1851: -------------------------------- Reducing the messages won't work: * A sends an mcast RSVP beacon * B creates an mcast RSVP entry, but doesn't send the beacon because A already did * The RSVP response is received and marks A's and B's entry as done * If B's message is dropped, we won't continue sending an mcast RSVP beacon for B, so B's message won't get retransmitted However, we could combine all RSVP beacon mesages to a given dest and send all of the IDs in an _array_ in *one beacon message* rather than in separate beacon messages. > RSVP: add option to not block caller > ------------------------------------ > > Key: JGRP-1851 > URL: https://issues.jboss.org/browse/JGRP-1851 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.6 > > > In RSVP we have a {{resend_interval}} at which empty messages are sent to trigger retransmission and a {{timeout}} which is the max time a caller will block until all acks have been received. > In the {{down()}} method, the caller blocks until all acks have been received or a timeout occured. Then the resend task is stopped and the entry removed from the {{ids}} map. > In some cases, we may want to not block the caller, so that the calling thread returns immediately, but nevertheless perform resending until all acks have been received or the timeout occurred. This is a new property {{block}}. > An example of where this is useful is {{RpcDispatcher.callRemoteMethodsWithFuture()}}: here, we want the call to return immediately with a future, and then - later - potentially block on it. However, if we have the RSVP flag set, then sending the message will block in RSVP until all acks have been received. This breaks the semantics of {{callRemoteMethodsWithFuture()}}. > Another example is async RPCs (mode={{GET_NONE}}); here we'd block if RSVP is set even though we shouldn't. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3357) Upgrade to JBoss NEgotiation 2.3.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3357?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3357: ----------------------------------------------- Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1097859|https://bugzilla.redhat.com/show_bug.cgi?id=1097859] from ON_QA to CLOSED > Upgrade to JBoss NEgotiation 2.3.1.Final > ---------------------------------------- > > Key: WFLY-3357 > URL: https://issues.jboss.org/browse/WFLY-3357 > Project: WildFly > Issue Type: Component Upgrade > Components: Server > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JGRP-1883) Extend SASL protocol to handle Quality of Protection

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/JGRP-1883?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on JGRP-1883: --------------------------------------- Using SASL for authentication makes it extremely simple to integrate it with WildFly's security realm, thus ensuring that role management is homogenous with the rest of the platform. Unfortunately, because of the PtP nature of the SASL QoP infrastructure it is not suitable for efficient group communication. For this reason, I really see no point in trying to shoehorn SASL as a replacement for ENCRYPT, and I'd much rather spend time describing why it is not suitable. > Extend SASL protocol to handle Quality of Protection > ----------------------------------------------------- > > Key: JGRP-1883 > URL: https://issues.jboss.org/browse/JGRP-1883 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.5 > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Fix For: 3.6 > > > SASL implementations generally provide authentication and encryption services to communication protocols. > At present, the JGroups SASL protocol layer handles only authentication of a client joining a group; it does not support encryption of messages (unicast and multicast) passing through the SASL layer. This is presently handled by the separate ENCRYPT layer. > It would be nice to provide an integrated and complete solution for authentication and encryption for JGroups based on SASL. This could be achieved by adding functionality from ENCRYPT to the SASL layer. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-129: ------------------------------------------------ baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1147353|https://bugzilla.redhat.com/show_bug.cgi?id=1147353] from NEW to ASSIGNED > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha9 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-129) Overlay does not work for subunits in exploded deployments.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-129?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-129: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147352, https://bugzilla.redhat.com/show_bug.cgi?id=1147353 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1147352) > Overlay does not work for subunits in exploded deployments. > ----------------------------------------------------------- > > Key: WFCORE-129 > URL: https://issues.jboss.org/browse/WFCORE-129 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha8 > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Fix For: 1.0.0.Alpha9 > > > If deployment is exploded and has subdeployments overlay wont work on files contained in said subdeployments. > Reproducers: https://github.com/baranowb/wildfly/tree/WFCORE-83-TESTS -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014