February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1294) Alias in jboss-cli are not persistent

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1294?page=com.atlassian.jira.plugi... ] Ståle Pedersen edited comment on WFCORE-1294 at 2/3/16 8:04 AM: ---------------------------------------------------------------- hi, sorry for not following this up, but this was merged into 0.66.3 and is in Wildfly10.0.0.Final However it seems that jboss-cli is not specifying the correct filename, this will be fixed in another version. was (Author: stalep): hi, sorry for not following this up, but this was merged into 0.66.3 and is in Wildfly10.0.0.Final > Alias in jboss-cli are not persistent > ------------------------------------- > > Key: WFCORE-1294 > URL: https://issues.jboss.org/browse/WFCORE-1294 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Alexis Hassler > Assignee: Ståle Pedersen > Fix For: 2.0.10.Final > > > Alias are supposed to be persistent in Aesh, but it fails due to a bug. This bug has been fix in Aesh but after version 0.66.2. > see AESH-341 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1294) Alias in jboss-cli are not persistent

by Ståle Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1294?page=com.atlassian.jira.plugi... ] Ståle Pedersen commented on WFCORE-1294: ---------------------------------------- hi, sorry for not following this up, but this was merged into 0.66.3 and is in Wildfly10.0.0.Final > Alias in jboss-cli are not persistent > ------------------------------------- > > Key: WFCORE-1294 > URL: https://issues.jboss.org/browse/WFCORE-1294 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.5.Final > Reporter: Alexis Hassler > Assignee: Ståle Pedersen > > Alias are supposed to be persistent in Aesh, but it fails due to a bug. This bug has been fix in Aesh but after version 0.66.2. > see AESH-341 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6117) Remove javax.transaction.api after it is moved to core

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6117?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-6117: ------------------------------ Description: The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it there, and then delete it from the main build. (was: The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it here.) > Remove javax.transaction.api after it is moved to core > ------------------------------------------------------ > > Key: WFLY-6117 > URL: https://issues.jboss.org/browse/WFLY-6117 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Fix For: 10.1.0.Final > > > The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it there, and then delete it from the main build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1358) Remove javax.transaction.api after it is moved to core

by David Lloyd (JIRA)

David Lloyd created WFCORE-1358: ----------------------------------- Summary: Remove javax.transaction.api after it is moved to core Key: WFCORE-1358 URL: https://issues.jboss.org/browse/WFCORE-1358 Project: WildFly Core Issue Type: Task Components: Modules Reporter: David Lloyd Fix For: 2.0.11.Final The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6117) Remove javax.transaction.api after it is moved to core

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6117?page=com.atlassian.jira.plugin.... ] David Lloyd moved WFCORE-1358 to WFLY-6117: ------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-6117 (was: WFCORE-1358) Component/s: (was: Modules) Fix Version/s: 10.1.0.Final (was: 2.0.11.Final) > Remove javax.transaction.api after it is moved to core > ------------------------------------------------------ > > Key: WFLY-6117 > URL: https://issues.jboss.org/browse/WFLY-6117 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Fix For: 10.1.0.Final > > > The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1357) Move javax.transaction.api to core

by David Lloyd (JIRA)

David Lloyd created WFCORE-1357: ----------------------------------- Summary: Move javax.transaction.api to core Key: WFCORE-1357 URL: https://issues.jboss.org/browse/WFCORE-1357 Project: WildFly Core Issue Type: Task Components: Modules Reporter: David Lloyd Fix For: 2.0.11.Final The javax.transaction.api module should be in core, because there are modules in core which depend on it. Move it here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1356) javax.sql.api should declare a dependency on javax.transaction.api

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1356?page=com.atlassian.jira.plugi... ] Tom Jenkinson commented on WFCORE-1356: --------------------------------------- [~jamezp] - the fix versions don't seem to have a 2.1.0? > javax.sql.api should declare a dependency on javax.transaction.api > ------------------------------------------------------------------ > > Key: WFCORE-1356 > URL: https://issues.jboss.org/browse/WFCORE-1356 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Labels: oracle-ucp > > javax.sql.XAConnection (https://docs.oracle.com/javase/7/docs/api/javax/sql/XAConnection.html) depends on javax.transaction.xa.XAResource > Including a partial stack trace that shows the failure: > {quote} > Caused by: java.lang.ClassNotFoundException: javax.transaction.xa.XAResource from [Module "javax.sql.api:main" from local module loader <SNIP/> > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1356) javax.sql.api should declare a dependency on javax.transaction.api

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1356?page=com.atlassian.jira.plugi... ] Tom Jenkinson moved JBEAP-3183 to WFCORE-1356: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-1356 (was: JBEAP-3183) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Modules (was: Class Loading) Target Release: (was: 7.0.0.GA) Affects Version/s: (was: 7.0.0.ER4) > javax.sql.api should declare a dependency on javax.transaction.api > ------------------------------------------------------------------ > > Key: WFCORE-1356 > URL: https://issues.jboss.org/browse/WFCORE-1356 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Labels: oracle-ucp > > javax.sql.XAConnection (https://docs.oracle.com/javase/7/docs/api/javax/sql/XAConnection.html) depends on javax.transaction.xa.XAResource > Including a partial stack trace that shows the failure: > {quote} > Caused by: java.lang.ClassNotFoundException: javax.transaction.xa.XAResource from [Module "javax.sql.api:main" from local module loader <SNIP/> > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4898) Change in permissions is not visible until server reload

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4898?page=com.atlassian.jira.plugin.... ] Tomas Hofman resolved WFLY-4898. -------------------------------- Fix Version/s: 10.0.0.Alpha6 Resolution: Done > Change in permissions is not visible until server reload > -------------------------------------------------------- > > Key: WFLY-4898 > URL: https://issues.jboss.org/browse/WFLY-4898 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Alpha4 > Reporter: Josef Cacek > Assignee: Tomas Hofman > Fix For: 10.0.0.Alpha6 > > > When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4898) Change in permissions is not visible until server reload

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4898?page=com.atlassian.jira.plugin.... ] Tomas Hofman commented on WFLY-4898: ------------------------------------ Note that deployment permission configuration was changed by WFLY-4880. Setting minimum permissions would now translate from {code} /subsystem=security-manager/deployment-permissions=default/minimum-set=default:add /subsystem=security-manager/deployment-permissions=default/minimum-set=default/permission=test:add(class=java.security.AllPermission) {code} to following: {code} /subsystem=security-manager/deployment-permissions=default:write-attribute(name=minimum-permissions, value=[{"class" => "java.security.AllPermission"}]) {code} Also, reload-required state is correctly set after above command is executed, so I'm marking the issue as Resolved. > Change in permissions is not visible until server reload > -------------------------------------------------------- > > Key: WFLY-4898 > URL: https://issues.jboss.org/browse/WFLY-4898 > Project: WildFly > Issue Type: Bug > Components: Security Manager > Affects Versions: 10.0.0.Alpha4 > Reporter: Josef Cacek > Assignee: Tomas Hofman > > When adding permissions in the security-manager subsystem, the changes are not used until server reload. But the CLI operation *doesn't require reload*. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016