March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-383) Re-Evaluate or Remove WebSecurityJBossWebXmlSecurityRolesTestCase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-383?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-383: ------------------------------ Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Re-Evaluate or Remove WebSecurityJBossWebXmlSecurityRolesTestCase > ----------------------------------------------------------------- > > Key: WFLY-383 > URL: https://issues.jboss.org/browse/WFLY-383 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 13.0.0.Beta1 > > > I have marked this test as "@Ignore"d as I do not believe the capability that is being tested is actually valid. > I can not find any evidence that we ever intended for a role to role mapping within the jboss-web.xml instead we only intended a principal to role mapping. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5141) Custom operation for setting of process-id-*

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5141?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5141: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Custom operation for setting of process-id-* > -------------------------------------------- > > Key: WFLY-5141 > URL: https://issues.jboss.org/browse/WFLY-5141 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Beta1 > Reporter: Ondra Chaloupka > Assignee: Amos Feng > Priority: Minor > Labels: ux > Fix For: 13.0.0.Beta1 > > > When you want to set generation of process-id-* - either as uuid or as socket id the way to set it and set it back is inconsistent. In one direction you need to use composite operation in other direction you can't use it. > All this is discussed in jiras WFLY-2623 and WFLY-5126 > As result of discussion https://issues.jboss.org/browse/WFLY-2623#comment-13100037 this issue is raised. > It would be much better for user to have single way how to do this switching and custom operation could solve this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4056) Graceful shutdown for JMS

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4056?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-4056: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Graceful shutdown for JMS > ------------------------- > > Key: WFLY-4056 > URL: https://issues.jboss.org/browse/WFLY-4056 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Stuart Douglas > Assignee: Jeff Mesnil > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3463) org.apache.cxf.wsdl11.WSDLManagerImpl needs read access to the jre wsdl.properties

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3463?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3463: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > org.apache.cxf.wsdl11.WSDLManagerImpl needs read access to the jre wsdl.properties > ---------------------------------------------------------------------------------- > > Key: WFLY-3463 > URL: https://issues.jboss.org/browse/WFLY-3463 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 9.0.0.CR1 > Reporter: Scott Marlow > Assignee: Alessio Soldano > Fix For: 13.0.0.Beta1 > > > During TCK testing (with security-manager enabled), I am seeing a java.security.AccessControlException: WFSM000001: Permission check failed for ("java.io.FilePermission" "/qa/tools/opt/x86_64/jdk1.7.0_60/jre/lib/wsdl.properties" "read") > from org.apache.cxf.wsdl11.WSDLManagerImpl. > Some related comments from irc: > {quote} > http://sourceforge.net/p/wsdl4j/patches/1/ > <asoldano> smarlow, I'm currently working around the problem (when running with security manager on) by setting "-Djavax.wsdl.factory.WSDLFactory=com.ibm.wsdl.factory.WSDLFactoryImpl" when starting the jvm > {quote} > Seems related to [https://issues.apache.org/jira/browse/TUSCANY-3925] which also has a patch. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3064) Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-3064?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-3064: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Remove org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase test case. > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-3064 > URL: https://issues.jboss.org/browse/WFLY-3064 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 13.0.0.Beta1 > > > A new test case was added under WFLY-3063 that demonstrates the correct way to do this so now remove the original way that depended on internal APIs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2102) Improve deployment annotation parsing error message

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2102?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2102: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Improve deployment annotation parsing error message > ----------------------------------------------------- > > Key: WFLY-2102 > URL: https://issues.jboss.org/browse/WFLY-2102 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Brad Maxwell > Fix For: 13.0.0.Beta1 > > Attachments: test-WFLY-2102.jar > > > Improve deployment annotation parsing error message > Code such as this below, will error with IllegalArgumentException: Empty name segment is not allowed for env. The env is not enough information to identify what the issue is. > @Singleton > @Startup > public class TestEJB { > @Resource(name="/queue/test") > private Queue queue; > } > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for env > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:141) > at org.jboss.as.ee.component.OptionalLookupInjectionSource.getResourceValue(OptionalLookupInjectionSource.java:84) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:1019) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:998) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:138) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5497) Add <distributable/> to shared-session-config schema

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5497?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5497: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Add <distributable/> to shared-session-config schema > ---------------------------------------------------- > > Key: WFLY-5497 > URL: https://issues.jboss.org/browse/WFLY-5497 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Web (Undertow) > Affects Versions: 10.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 13.0.0.Beta1 > > > Currently, the shared-session-config does not indicate whether a distributable or non-distributable session manager should be used. Consequently, we assign the session manager implementation based on the availability of the module providing the distributed implementation. Since the default infinispan web session configuration attempts to passivate sessions on shutdown, users will see NotSerializableExceptions on shutdown if they use non-serializable session attributes - even if their web applications do not define themselves as being <distributable/>. > To clarify this ambiguity, we should add a <distributable/> element (a la web.xml) to the shared-session-config schema to determine which session manager implementation to use. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5427) If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5427?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5427: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > If used journal object store (AMQ Artemis journal) directory is named HornetqObjectStore > ---------------------------------------------------------------------------------------- > > Key: WFLY-5427 > URL: https://issues.jboss.org/browse/WFLY-5427 > Project: WildFly > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.CR2 > Reporter: Ondra Chaloupka > Assignee: Amos Feng > Priority: Minor > Fix For: 13.0.0.Beta1 > > > Directory of transaction object store is named {{standalone/data/tx-object-store/HornetqObjectStore}}. The WFLY 10 does not use HornetQ object store but it uses ActiveMQ Artemis object store. That's same for the Transaction subsystem. > The journal dirctory should be renamed to {{JournalObjectStore}} or something similar. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5406) Update to add a testcase for the journal store setting in the transaction subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5406?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5406: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Update to add a testcase for the journal store setting in the transaction subsystem > ----------------------------------------------------------------------------------- > > Key: WFLY-5406 > URL: https://issues.jboss.org/browse/WFLY-5406 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, Transactions > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5265) Use WildFly Common for null param checks

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-5265?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-5265: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Use WildFly Common for null param checks > ---------------------------------------- > > Key: WFLY-5265 > URL: https://issues.jboss.org/browse/WFLY-5265 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Minor > Fix For: 13.0.0.Beta1 > > > For each module, do the following: > * Locate any/all null param check methods in the log msg > * Replace them with calls to org.wildfly.common.Assert#checkNotNullParam or related method as needed > * Replace the old null param check method with a comment that reserves the ID and shows that it was previously used for that purpose -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 March 2018