June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2966) WildFly Elytron tool script has to pass the command name from the script to the tool.

by Ilia Vassilev (JIRA)

Ilia Vassilev created WFCORE-2966: ------------------------------------- Summary: WildFly Elytron tool script has to pass the command name from the script to the tool. Key: WFCORE-2966 URL: https://issues.jboss.org/browse/WFCORE-2966 Project: WildFly Core Issue Type: Bug Components: Security Affects Versions: 3.0.0.Beta26 Reporter: Ilia Vassilev Assignee: Darran Lofthouse WildFly Elytron tool script has to pass the command name from the script to the tool in the format of {script_name}. This issue depends on the implementation of ELY-1228. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet

by Cody Lerum (JIRA)

[ https://issues.jboss.org/browse/WFLY-8942?page=com.atlassian.jira.plugin.... ] Cody Lerum commented on WFLY-8942: ---------------------------------- Also see: https://twitter.com/codylerum/status/875450481170030592 > Request Scope is not active during Batchlet > ------------------------------------------- > > Key: WFLY-8942 > URL: https://issues.jboss.org/browse/WFLY-8942 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 10.1.0.Final > Environment: Wildfly 10.1.0 Final > Reporter: Cody Lerum > Assignee: Cheng Fang > > When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted. > Example > {noformat} > 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped > at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689) > at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90) > at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165) > at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63) > at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8942) Request Scope is not active during Batchlet

by Cody Lerum (JIRA)

Cody Lerum created WFLY-8942: -------------------------------- Summary: Request Scope is not active during Batchlet Key: WFLY-8942 URL: https://issues.jboss.org/browse/WFLY-8942 Project: WildFly Issue Type: Bug Components: Batch Affects Versions: 10.1.0.Final Environment: Wildfly 10.1.0 Final Reporter: Cody Lerum Assignee: Cheng Fang When executing a Java EE 7 batchlet if an injection of an @RequestScoped bean is attempted. Example {noformat} 20:57:13,995 WARN [org.jberet] (Batch Thread - 13) JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@b5b6a97: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.enterprise.context.RequestScoped at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:689) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:90) at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.getIfExists(ContextualInstanceStrategy.java:165) at org.jboss.weld.bean.ContextualInstance.getIfExists(ContextualInstance.java:63) at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:83) at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125) {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2965) Building server boot commands in the HC may use the incorrect logging.properties on initial boot

by Martin Simka (JIRA)

Martin Simka created WFCORE-2965: ------------------------------------ Summary: Building server boot commands in the HC may use the incorrect logging.properties on initial boot Key: WFCORE-2965 URL: https://issues.jboss.org/browse/WFCORE-2965 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Martin Simka Assignee: James Perkins When the HC builds the boot commands for a server on initial boot there is no {{logging.properties}} file in the servers data directory. There's an attempt to discover which configuration file would be used. On some OS's the paths may be the same, but the string representation may be different due to different file separators. When attempting to decide which logging configuration file to use the match may fail which will lead to an incorrect configuration file being used on initial boot only. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2964) Building server boot commands in the HC may use the incorrect logging.properties on initial boot

by James Perkins (JIRA)

James Perkins created WFCORE-2964: ------------------------------------- Summary: Building server boot commands in the HC may use the incorrect logging.properties on initial boot Key: WFCORE-2964 URL: https://issues.jboss.org/browse/WFCORE-2964 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: James Perkins When the HC builds the boot commands for a server on initial boot there is no {{logging.properties}} file in the servers data directory. There's an attempt to discover which configuration file would be used. On some OS's the paths may be the same, but the string representation may be different due to different file separators. When attempting to decide which logging configuration file to use the match may fail which will lead to an incorrect configuration file being used on initial boot only. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8941) Fix model versions for all subsystems so transformers can be properly written

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8941: --------------------------------- Summary: Fix model versions for all subsystems so transformers can be properly written Key: WFLY-8941 URL: https://issues.jboss.org/browse/WFLY-8941 Project: WildFly Issue Type: Bug Reporter: Tomaz Cerar Assignee: Tomaz Cerar Currently we have few subsystems that had wrongly bumped only minor model version instead of major as the change is coming in next major WildFly version. full list of model version can be found at https://github.com/wildfly/wildfly-legacy-test/wiki/EAP-7.0.0.GA-vs-EAP-7... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8940) Transformers for EJB3 subsystem

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8940: --------------------------------- Summary: Transformers for EJB3 subsystem Key: WFLY-8940 URL: https://issues.jboss.org/browse/WFLY-8940 Project: WildFly Issue Type: Sub-task Reporter: Tomaz Cerar Assignee: Tomaz Cerar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8870) AuthenticationTestCase fails with security manager

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8870?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-8870: --------------------------------- Assignee: (was: Tomaz Cerar) > AuthenticationTestCase fails with security manager > -------------------------------------------------- > > Key: WFLY-8870 > URL: https://issues.jboss.org/browse/WFLY-8870 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 11.0.0.Beta1 > Reporter: Ondrej Kotek > > *org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase* > There are missing permissions: > * {{new PropertyPermission("jboss.bind.address", "read")}} required by {{TestSuiteEnvironment}} class, > * {{new ElytronPermission("getSecurityDomain")}}, > * {{new ElytronPermission("authenticate")}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8870) AuthenticationTestCase fails with security manager

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8870?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-8870: ------------------------------ Component/s: Security Manager > AuthenticationTestCase fails with security manager > -------------------------------------------------- > > Key: WFLY-8870 > URL: https://issues.jboss.org/browse/WFLY-8870 > Project: WildFly > Issue Type: Bug > Components: Security Manager, Test Suite > Affects Versions: 11.0.0.Beta1 > Reporter: Ondrej Kotek > > *org.wildfly.test.integration.elytron.ejb.AuthenticationTestCase* > There are missing permissions: > * {{new PropertyPermission("jboss.bind.address", "read")}} required by {{TestSuiteEnvironment}} class, > * {{new ElytronPermission("getSecurityDomain")}}, > * {{new ElytronPermission("authenticate")}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1246) The elytron-1_0.xsd has elements the parser does not accept

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/ELY-1246?page=com.atlassian.jira.plugin.s... ] James Perkins moved JBEAP-11587 to ELY-1246: -------------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1246 (was: JBEAP-11587) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Target Release: (was: 7.1.0.GA) > The elytron-1_0.xsd has elements the parser does not accept > ----------------------------------------------------------- > > Key: ELY-1246 > URL: https://issues.jboss.org/browse/ELY-1246 > Project: WildFly Elytron > Issue Type: Bug > Reporter: James Perkins > > There are elements in the {{elytron-1_0.xsd}} that the parser does not accept. While I didn't check them all here are at least a few that are in the XSD that the parser will reject: > * {{allow-sasl-mechanisms}} > * {{allow-all-sasl-mechanisms}} > * {{forbid-sasl-mechanisms}} > This may be all of them, but it should likely be validated that those are the only ones. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 June 2017