February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8053) Warn user when configuration change might make server inoperable

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/WFLY-8053?page=com.atlassian.jira.plugin.... ] Bartosz Baranowski reassigned WFLY-8053: ---------------------------------------- Assignee: Bartosz Baranowski (was: Jason Greene) > Warn user when configuration change might make server inoperable > ---------------------------------------------------------------- > > Key: WFLY-8053 > URL: https://issues.jboss.org/browse/WFLY-8053 > Project: WildFly > Issue Type: Enhancement > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8122) Backport Latest Elytron and Invocation Integration Changes

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-8122: -------------------------------------- Summary: Backport Latest Elytron and Invocation Integration Changes Key: WFLY-8122 URL: https://issues.jboss.org/browse/WFLY-8122 Project: WildFly Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7168) Complex type sasl-authentication-factory in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7168?page=com.atlassian.jira.plugin.... ] Jan Kalina closed WFLY-7168. ---------------------------- Resolution: Rejected As discussed in JBEAP-6100, change of complex attributes to subresources would not have supposed positive consequences - closing. > Complex type sasl-authentication-factory in Elytron subsystem > ------------------------------------------------------------- > > Key: WFLY-7168 > URL: https://issues.jboss.org/browse/WFLY-7168 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Elytron subsystem uses complex type in sasl-authentication-factory resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. > Complex attributes in add operation and resource description: > mechanism-configurations > mechanism-realm-configurations -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7164) Complex type http-authentication-factory in Elytron subsystem

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7164?page=com.atlassian.jira.plugin.... ] Jan Kalina closed WFLY-7164. ---------------------------- Resolution: Rejected As discussed in JBEAP-6100, change of complex attributes to subresources would not have supposed positive consequences - closing. > Complex type http-authentication-factory in Elytron subsystem > ------------------------------------------------------------- > > Key: WFLY-7164 > URL: https://issues.jboss.org/browse/WFLY-7164 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 11.0.0.Alpha1 > > > Elytron subsystem uses complex type in http-authentication-factory resource which is difficult to use and can result to bad user experience, see description of JBEAP-6100 for more details. > Complex attributes in add operation and resource description: > mechanism-configurations > mechanism-realm-configurations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-964) Coverity static analysis, Resource leak on an exceptional path, FileAuditEndpoint (elytron)

by Martin Choma (JIRA)

Martin Choma created ELY-964: -------------------------------- Summary: Coverity static analysis, Resource leak on an exceptional path, FileAuditEndpoint (elytron) Key: ELY-964 URL: https://issues.jboss.org/browse/ELY-964 Project: WildFly Elytron Issue Type: Bug Reporter: Martin Choma Assignee: Darran Lofthouse Coverity static analysis found possible occurence of resource leak. https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=96902... In constructor when {{fos.getFD()}} will throw exception {{FileOutputStream fos}} won't be closed. {code:java|title=FileAuditEndpoint.java} FileAuditEndpoint(Builder builder) throws IOException { this.dateFormatSupplier = builder.dateFormatSupplier; this.syncOnAccept = builder.syncOnAccept; FileOutputStream fos = new FileOutputStream(builder.location.toFile(), true); this.fileDescriptor = fos.getFD(); this.outputStream = new BufferedOutputStream(fos); } {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8109) Improve timeouts in AS TS

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-8109?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFLY-8109: -------------------------------- Description: Improve timeouts in AS TS * JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout * increase timeout in PassivationTestCase * JspCompilerTestCase should use TimeoutUtil for timeout * increase timeout in MDBTestCase * increase the default forked process timeout for basic module to hour, [same timeout is used in clustering module|https://github.com/wildfly/wildfly/blob/master/testsuite/integrati...] This stabilizes TS on slower machines. was: Improve timeouts in AS TS * JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout * increase timeout in PassivationTestCase * JspCompilerTestCase should use TimeoutUtil for timeout * increase timeout in MDBTestCase * increase the default forked process timeout for basic module to hour, [same timeout is used in clustering module|https://github.com/jbossas/jboss-eap7/blob/7.x/testsuite/integrati...] This stabilizes TS on slower machines. > Improve timeouts in AS TS > ------------------------- > > Key: WFLY-8109 > URL: https://issues.jboss.org/browse/WFLY-8109 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > Improve timeouts in AS TS > * JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout > * increase timeout in PassivationTestCase > * JspCompilerTestCase should use TimeoutUtil for timeout > * increase timeout in MDBTestCase > * increase the default forked process timeout for basic module to hour, [same timeout is used in clustering module|https://github.com/wildfly/wildfly/blob/master/testsuite/integrati...] > This stabilizes TS on slower machines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8109) Improve timeouts in AS TS

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFLY-8109?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFLY-8109: -------------------------------- Description: Improve timeouts in AS TS * JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout * increase timeout in PassivationTestCase * JspCompilerTestCase should use TimeoutUtil for timeout * increase timeout in MDBTestCase * increase the default forked process timeout for basic module to hour, [same timeout is used in clustering module|https://github.com/jbossas/jboss-eap7/blob/7.x/testsuite/integrati...] This stabilizes TS on slower machines. was: Improve timeouts in AS TS * JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout * increase timeout in PassivationTestCase * JspCompilerTestCase should use TimeoutUtil for timeout * increase timeout in MDBTestCase * increase timeout in LegacyConfigTest * increase timeout in DomainHostExcludesTest * increase the default forked process timeout for basic module to hour, [same timeout is used in clustering module|https://github.com/jbossas/jboss-eap7/blob/7.x/testsuite/integrati...] This stabilizes TS on slower machines. > Improve timeouts in AS TS > ------------------------- > > Key: WFLY-8109 > URL: https://issues.jboss.org/browse/WFLY-8109 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Marek Kopecký > Assignee: Marek Kopecký > > Improve timeouts in AS TS > * JMSMessageDrivenBeanTestCase should use TimeoutUtil for timeout > * increase timeout in PassivationTestCase > * JspCompilerTestCase should use TimeoutUtil for timeout > * increase timeout in MDBTestCase > * increase the default forked process timeout for basic module to hour, [same timeout is used in clustering module|https://github.com/jbossas/jboss-eap7/blob/7.x/testsuite/integrati...] > This stabilizes TS on slower machines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8121) WeldDeployment.loadBeanDeploymentArchive() may create multiple bean deployment archives with the same id

by Martin Kouba (JIRA)

Martin Kouba created WFLY-8121: ---------------------------------- Summary: WeldDeployment.loadBeanDeploymentArchive() may create multiple bean deployment archives with the same id Key: WFLY-8121 URL: https://issues.jboss.org/browse/WFLY-8121 Project: WildFly Issue Type: Bug Components: CDI / Weld Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 11.0.0.Alpha1 This does not match the {{org.jboss.weld.bootstrap.spi.BeanDeploymentArchive}} contract. The use case is described in https://issues.jboss.org/browse/WELD-2165?focusedCommentId=13286271&page=.... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1805) It should be possible to pass objects via invocation context from the server side EJB to the client and read with a via client side interceptor

by Teresa Miyar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1805?page=com.atlassian.jira.plugin.... ] Teresa Miyar updated WFLY-1805: ------------------------------- SourceForge Reference: https://access.redhat.com/support/cases/01682712 > It should be possible to pass objects via invocation context from the server side EJB to the client and read with a via client side interceptor > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1805 > URL: https://issues.jboss.org/browse/WFLY-1805 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Labels: ejb > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8120) Upgrade picketlink 2.5.5.SP5 to 2.5.5.SP6

by Lin Gao (JIRA)

Lin Gao created WFLY-8120: ----------------------------- Summary: Upgrade picketlink 2.5.5.SP5 to 2.5.5.SP6 Key: WFLY-8120 URL: https://issues.jboss.org/browse/WFLY-8120 Project: WildFly Issue Type: Component Upgrade Components: Security Reporter: Lin Gao Assignee: Kabir Khan -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 2017