May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-390) Add reference description information to resource metadata

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-390?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-390: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Add reference description information to resource metadata > ---------------------------------------------------------- > > Key: WFCORE-390 > URL: https://issues.jboss.org/browse/WFCORE-390 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha4 > > > The AS's configuration model frequently includes attributes that are references to the name of some other resource in the model. The metadata describing such attributes must include information to help users and tooling to understand that reference. > A simple approach would be to include a metadata attribute whose value is an absolute or relative path to the target resource. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-703) An ObjectTypeAttributeDefinition should recursively handle a resolveModelAttribute call.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-703?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-703: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > An ObjectTypeAttributeDefinition should recursively handle a resolveModelAttribute call. > ---------------------------------------------------------------------------------------- > > Key: WFCORE-703 > URL: https://issues.jboss.org/browse/WFCORE-703 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 2.0.0.Alpha4 > > > Expressions will be handled recursively but the default values for the contained AttributeDefinitions should also be recursively handled so that the returned ModelNode is fully populated with both resolved expressions and default values. > Other variants of attributes such as the lists and maps should also be double checked to ensure they are recursive. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-688) Remove ServerEnvironment.getModulesDir()

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-688?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-688: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Remove ServerEnvironment.getModulesDir() > ---------------------------------------- > > Key: WFCORE-688 > URL: https://issues.jboss.org/browse/WFCORE-688 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 2.0.0.Alpha4 > > > This method was deprecated in 7.1.0 and the OSGi subsystem is removing the only known use of it in 7.1.2. Remove the method in 7.2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-683) ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-683?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-683: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > ListModuleRootsHandler and ModuleLocationHandler don't handle PrivilegedActionException properly > ------------------------------------------------------------------------------------------------ > > Key: WFCORE-683 > URL: https://issues.jboss.org/browse/WFCORE-683 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.CR1 > Reporter: Brian Stansberry > Fix For: 2.0.0.Alpha4 > > > The two inner class OSHs in ModuleLoadingResourceDefinition don't deal with exceptions properly. They invoke AccessController.doPrivileged and then deal with any PrivilegedActionException by rethrowing as OperationFailedException. > OperationFailedException represents a client mistake and is handled as such (e.g. isn't logged in the server log.) It shouldn't be thrown here unless the PrivilegedActionException.getCause() value is itself an OFE. Otherwise, the OSHs should throw a RuntimeException. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-646) Product to Project Schema and Model Sync

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-646?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-646: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Product to Project Schema and Model Sync > ---------------------------------------- > > Key: WFCORE-646 > URL: https://issues.jboss.org/browse/WFCORE-646 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > > Periodic sync of EAP schemas with WildFly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-610) Integrate Elytron for management security.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-610?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-610: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Integrate Elytron for management security. > ------------------------------------------ > > Key: WFCORE-610 > URL: https://issues.jboss.org/browse/WFCORE-610 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > > This is a top level container task for the integration of Elytron for domain management security. > Do note however that the purpose of Elytron is a single unified security solution across the whole of the application server so many tasks here will be groundwork for the remainder of the integration. > At the moment the Elytron subsystem is being developed outside of wildfly-core, this will need to change in the future due to dependency issues (i.e. to write a subsystem you need to depend on core and core will need to include the subsystem (I think.)). However this will make it easier for now to ensure that the subsystem is 100% with no WildFly code accessing the subsystem - and also verify that we can create a distribtion with out the subsystem and still have a functional server. > Overall if someone came up with an alternative subsystem that provided the same capabilities it should be possible to drop it in. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-609) Administrator Encouragement

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-609?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-609: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Administrator Encouragement > --------------------------- > > Key: WFCORE-609 > URL: https://issues.jboss.org/browse/WFCORE-609 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > > I know the name is not popular so will have a better name ;-) > Essentially some form of centralised repository to hold warnings raised by subsystems as a server boots. > Management operations would be provided to query the current warnings. > As administrators undertake actions to correct a warning it will be dynamically removed by the subsystem that reported it. > This is not about persistent warnings i.e. the subsystem should raise the warning on every boot and stop raising it if it is no longer relevant. > e.g. SSL not enabled, warn every time the server starts until it is enabled. > Warnings will be associated with a severity level and administrative tooling can decide how pro-actively to display the warning, e.g. the console may pop up immediately for a critical warning or use an icon to indicate the presence of a lesser warning. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-719) JDK 1.8 javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-719?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-719: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > JDK 1.8 javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > --------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-719 > URL: https://issues.jboss.org/browse/WFCORE-719 > Project: WildFly Core > Issue Type: Enhancement > Affects Versions: 2.0.0.Alpha2 > Reporter: Manuel Blechschmidt > Assignee: Tomaz Cerar > Labels: JS223, JavaScript, Scripting > Fix For: 2.0.0.Alpha4 > > > When using the ScriptManager in a JSF bean the following happens: > ERROR [stderr] (default task-21) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > {code} > package de.example.log.jsf; > import java.io.ByteArrayOutputStream; > import java.io.IOException; > import java.io.PrintStream; > import javax.enterprise.inject.Model; > import javax.faces.application.FacesMessage; > import javax.faces.context.FacesContext; > import javax.inject.Inject; > import javax.script.Bindings; > import javax.script.ScriptEngine; > import javax.script.ScriptEngineManager; > import javax.script.ScriptException; > @Model > public class Scripting { > private String script; > private String output; > private ScriptEngineManager mgr = new ScriptEngineManager(); > public static String utilJavaScript = "var print = function (s) { __newOut.print(s); }; var println = function (s) { __newOut.println(s); };"; > public String execute() { > ScriptEngine jsEngine = mgr.getEngineByName("JavaScript"); > ByteArrayOutputStream outputBuffer = new ByteArrayOutputStream(8192); > PrintStream newOut = new PrintStream(outputBuffer, true); > Bindings bindings = jsEngine.createBindings(); > bindings.put("__newOut", newOut); > try { > jsEngine.eval(utilJavaScript + getScript(), bindings); > } catch (ScriptException from) { > FacesContext.getCurrentInstance().addMessage( > null, > new FacesMessage(from.getColumnNumber() + " " > + from.getFileName() + " " + from.getLineNumber() > + " " + from.getMessage())); > return null; > } > newOut.close(); > String returnString = outputBuffer.toString(); > setOutput(returnString); > try { > outputBuffer.close(); > } catch (IOException e) { > FacesContext.getCurrentInstance().addMessage( > null, > new FacesMessage(e.getLocalizedMessage())); > } > return null; > } > public String getScript() { > return script; > } > public void setScript(String script) { > this.script = script; > } > public String getOutput() { > return output; > } > public void setOutput(String output) { > this.output = output; > } > } > {code} > The script engines are configured in the following file: > WILDFLY_HOME/modules/system/layers/base/sun/jdk/main/service-loader-resources/META-INF/services/javax.script.ScriptEngineFactory > {code} > com.sun.script.javascript.RhinoScriptEngineFactory > jdk.nashorn.api.scripting.NashornScriptEngineFactory > {code} > It should be made sure that with every JDK JSR 223 compliant requests for a JavaScript engine will work out of the box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-716) Once server in reload-required state capabilities no longer checked at stage Model.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-716?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-716: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Once server in reload-required state capabilities no longer checked at stage Model. > ----------------------------------------------------------------------------------- > > Key: WFCORE-716 > URL: https://issues.jboss.org/browse/WFCORE-716 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.0.0.Alpha2 > Reporter: Darran Lofthouse > Assignee: Brian Stansberry > Labels: affects_elytron > Fix For: 2.0.0.Alpha4 > > > Once a server is in the state reload-required capabilities and requirements are no longer checked e.g.: - > {noformat} > [standalone@localhost:9990 /] ./core-service=management/management-interface=http-interface:undefine-attribute(name=security-realm) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > The following command is referencing a non-existent capability: - > {noformat} > [standalone@localhost:9990 /] ./core-service=management/management-interface=http-interface:write-attribute(name=security-domain, value=MgMtDom) > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} > When I execute :reload it will fail: - > {noformat} > 11:21:18,567 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("management-interface" => "http-interface") > ]): java.lang.IllegalStateException: WFLYCTL0364: Capability 'org.wildfly.security.security-domain.MgMtDom' is unknown. > at org.jboss.as.controller.ModelControllerImpl$CapabilityRegistryImpl.getCapabilityRegistration(ModelControllerImpl.java:1388) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-714) Integrate Elytron with the Remoting subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFCORE-714?page=com.atlassian.jira.plugin... ] Jason Greene updated WFCORE-714: -------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Integrate Elytron with the Remoting subsystem > --------------------------------------------- > > Key: WFCORE-714 > URL: https://issues.jboss.org/browse/WFCORE-714 > Project: WildFly Core > Issue Type: Sub-task > Components: Remoting, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

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 May 2015