July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5497) Stunner Palette: Hovering text not showing in Firefox 77.0.1

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5497?page=com.atlassian.jira.plug... ] Mario Fusco reassigned DROOLS-5497: ----------------------------------- Assignee: Mario Fusco (was: Roger Martinez) > Stunner Palette: Hovering text not showing in Firefox 77.0.1 > ------------------------------------------------------------ > > Key: DROOLS-5497 > URL: https://issues.redhat.com/browse/DROOLS-5497 > Project: Drools > Issue Type: Enhancement > Components: Stunner > Reporter: Luca Molteni > Assignee: Mario Fusco > Priority: Major > Attachments: hovering.webm > > > Video attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5497) Stunner Palette: Hovering text not showing in Firefox 77.0.1

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5497?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-5497: -------------------------------------- Assignee: Roger Martinez (was: Mario Fusco) > Stunner Palette: Hovering text not showing in Firefox 77.0.1 > ------------------------------------------------------------ > > Key: DROOLS-5497 > URL: https://issues.redhat.com/browse/DROOLS-5497 > Project: Drools > Issue Type: Enhancement > Components: Stunner > Reporter: Luca Molteni > Assignee: Roger Martinez > Priority: Major > Attachments: hovering.webm > > > Video attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5497) Stunner Palette: Hovering text not showing in Firefox 77.0.1

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5497?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5497: ----------------------------------- Summary: Stunner Palette: Hovering text not showing in Firefox 77.0.1 (was: Hovering text not showing in Firefox 77.0.1) > Stunner Palette: Hovering text not showing in Firefox 77.0.1 > ------------------------------------------------------------ > > Key: DROOLS-5497 > URL: https://issues.redhat.com/browse/DROOLS-5497 > Project: Drools > Issue Type: Enhancement > Components: Stunner > Reporter: Luca Molteni > Assignee: Mario Fusco > Priority: Major > Attachments: hovering.webm > > > Video attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5497) Hovering text not showing in Firefox 77.0.1

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5497?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5497: --------------------------------- Attachment: hovering.webm > Hovering text not showing in Firefox 77.0.1 > ------------------------------------------- > > Key: DROOLS-5497 > URL: https://issues.redhat.com/browse/DROOLS-5497 > Project: Drools > Issue Type: Enhancement > Components: Stunner > Reporter: Luca Molteni > Assignee: Mario Fusco > Priority: Major > Attachments: hovering.webm > > > Video attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5497) Hovering text not showing in Firefox 77.0.1

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5497: ------------------------------------ Summary: Hovering text not showing in Firefox 77.0.1 Key: DROOLS-5497 URL: https://issues.redhat.com/browse/DROOLS-5497 Project: Drools Issue Type: Enhancement Components: Stunner Reporter: Luca Molteni Assignee: Mario Fusco Attachments: hovering.webm Video attached -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1195) Add OCP 4.6 to our jenkins provisioning jobs

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1195: ------------------------------------ Summary: Add OCP 4.6 to our jenkins provisioning jobs Key: SWSQE-1195 URL: https://issues.redhat.com/browse/SWSQE-1195 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml

by Matěj Novotný (Jira)

[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-13641: -------------------------------------- I see, good catch! According to that, those beans shouldn't be picked up at all. Looking at {{ExternalBeanArchiveProcessor}}, there is no processing regarding jboss-deployment-structure so that has to be done earlier (don't know where yet). This processor works on the deployment unit and all its subdeployments and dependencies. Maybe you have some dependency between the two projects that causes the other project to be scanned for beans as well? The reproducer you mentioned would be neat. > WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13641 > URL: https://issues.redhat.com/browse/WFLY-13641 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 20.0.0.Final > Reporter: Jens Viebig > Assignee: Matěj Novotný > Priority: Major > > When referencing a jar with CDI scan mode "annotaded" inside an ear from an external war via jboss-deployment-structure.xml a warning will be printed for every class: > WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml > Seems VFS cannot get hold of the classes. > The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from the inputstream loading the class. (Line 284). Seems the input stream is not able to load a single byte from the class -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4863) Upgrade PicketBox to 5.0.3.Final-redhat-00006

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4863?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4863: -------------------------------- Fix Version/s: 13.0.0.Beta2 > Upgrade PicketBox to 5.0.3.Final-redhat-00006 > --------------------------------------------- > > Key: WFCORE-4863 > URL: https://issues.redhat.com/browse/WFCORE-4863 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Labels: downstream_dependency > Fix For: 13.0.0.Beta2 > > > Branch: https://github.com/jbossas/redhat-picketbox/tree/5.0.x -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5022) The /subsystem=elytron/policy=* can be simplified a lot further

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5022?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5022: -------------------------------- Fix Version/s: (was: 13.0.0.Beta1) > The /subsystem=elytron/policy=* can be simplified a lot further > --------------------------------------------------------------- > > Key: WFCORE-5022 > URL: https://issues.redhat.com/browse/WFCORE-5022 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Affects Versions: 12.0.1.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta2 > > > At the moment this resource is quite verbose but the tasks it performs are very simple. > {code} > [standalone@localhost:9990 /] /subsystem=elytron/policy=*:read-resource-description > { > "outcome" => "success", > "result" => [{ > "address" => [ > ("subsystem" => "elytron"), > ("policy" => "*") > ], > "outcome" => "success", > "result" => { > "description" => "A definition that sets up a policy provider.", > "max-occurs" => 1, > "capabilities" => [{ > "name" => "org.wildfly.security.policy", > "dynamic" => false > }], > "access-constraints" => { > "sensitive" => {"elytron-security" => {"type" => "elytron"}}, > "application" => {"elytron-security" => {"type" => "elytron"}} > }, > "attributes" => { > "custom-policy" => { > "type" => OBJECT, > "description" => "A custom policy provider definition.", > "expressions-allowed" => false, > "required" => true, > "nillable" => true, > "alternatives" => ["jacc-policy"], > "value-type" => { > "class-name" => { > "type" => STRING, > "description" => "The name of a java.security.Policy implementation referencing a policy provider.", > "expressions-allowed" => false, > "required" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > }, > "module" => { > "type" => STRING, > "description" => "The name of the module to load the provider from.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > } > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > "default-policy" => { > "type" => STRING, > "description" => "Not used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "1.2.0", > "reason" => "The 'default-policy' attribute is ignored, as a policy resource should be configured with only one policy." > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > "jacc-policy" => { > "type" => OBJECT, > "description" => "A policy provider definition that sets up JACC and related services.", > "expressions-allowed" => false, > "required" => true, > "nillable" => true, > "alternatives" => ["custom-policy"], > "value-type" => { > "policy" => { > "type" => STRING, > "description" => "The name of a java.security.Policy implementation referencing a policy provider.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => "org.wildfly.security.authz.jacc.JaccDelegatingPolicy", > "min-length" => 1L, > "max-length" => 2147483647L > }, > "configuration-factory" => { > "type" => STRING, > "description" => "The name of a javax.security.jacc.PolicyConfigurationFactory implementation referencing a policy configuration factory provider.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => "org.wildfly.security.authz.jacc.ElytronPolicyConfigurationFactory", > "min-length" => 1L, > "max-length" => 2147483647L > }, > "module" => { > "type" => STRING, > "description" => "The name of the module to load the provider from.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > } > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {} > } > }] > } > {code} > Firstly it only makes sense to have a single policy defined, the outcome of this resource is JVM wide registration so multiple definitions would lead to undefined behaviour. > Secondly this provides two primary functions. > 1. Instantation of https://docs.oracle.com/javase/8/docs/api/java/security/Policy.html and registration via a call to https://docs.oracle.com/javase/8/docs/api/java/security/Policy.html#setPo... > This first point needs a class name for the policy as well as a module. > 2. Registration of the JVM wide https://jakarta.ee/specifications/platform/8/apidocs/javax/security/jacc/... again needing a classname and module. > This is also not working correctly but the immediate bug is being addressed under WFCORE-5020 > The JACC APIs don't actually provide a nice way to register this so maybe this is something we should also propose via the spec, but this piece is effectively a class name and module name. > We have ended up with custom and jacc variants as alternatives. Really both variants are optional but if the resource is defined at least one must be set. > It may make sense for JACC to move to it's own subsystem for a couple of reasons. > The JVM wide policy will likely need to be possible in both subsystems but use a capability to ensure it is defined in only one. We probably should move it's registration into the boot operations so registration is complete before DUPs begin. > The PolicyConfigurationFactory would then be in a JACC subsystem only. Again handling during a boot operation may be preferable otherwise we see issues like WFLY-13615 but failing that ensuring the deployment depend upon the registration happening may be sufficient. > Additionally the resource has some hard coded class names for the Policy and PolicyConfigurationFactory, we probably should not have these as class names and instead default to them if not defined - this means we still need a way to optionally activate their registration if JACC is required on the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5022) The /subsystem=elytron/policy=* can be simplified a lot further

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5022?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5022: -------------------------------- Fix Version/s: 13.0.0.Beta2 > The /subsystem=elytron/policy=* can be simplified a lot further > --------------------------------------------------------------- > > Key: WFCORE-5022 > URL: https://issues.redhat.com/browse/WFCORE-5022 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Affects Versions: 12.0.1.Final > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 13.0.0.Beta1, 13.0.0.Beta2 > > > At the moment this resource is quite verbose but the tasks it performs are very simple. > {code} > [standalone@localhost:9990 /] /subsystem=elytron/policy=*:read-resource-description > { > "outcome" => "success", > "result" => [{ > "address" => [ > ("subsystem" => "elytron"), > ("policy" => "*") > ], > "outcome" => "success", > "result" => { > "description" => "A definition that sets up a policy provider.", > "max-occurs" => 1, > "capabilities" => [{ > "name" => "org.wildfly.security.policy", > "dynamic" => false > }], > "access-constraints" => { > "sensitive" => {"elytron-security" => {"type" => "elytron"}}, > "application" => {"elytron-security" => {"type" => "elytron"}} > }, > "attributes" => { > "custom-policy" => { > "type" => OBJECT, > "description" => "A custom policy provider definition.", > "expressions-allowed" => false, > "required" => true, > "nillable" => true, > "alternatives" => ["jacc-policy"], > "value-type" => { > "class-name" => { > "type" => STRING, > "description" => "The name of a java.security.Policy implementation referencing a policy provider.", > "expressions-allowed" => false, > "required" => true, > "nillable" => false, > "min-length" => 1L, > "max-length" => 2147483647L > }, > "module" => { > "type" => STRING, > "description" => "The name of the module to load the provider from.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > } > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > "default-policy" => { > "type" => STRING, > "description" => "Not used.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L, > "deprecated" => { > "since" => "1.2.0", > "reason" => "The 'default-policy' attribute is ignored, as a policy resource should be configured with only one policy." > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > }, > "jacc-policy" => { > "type" => OBJECT, > "description" => "A policy provider definition that sets up JACC and related services.", > "expressions-allowed" => false, > "required" => true, > "nillable" => true, > "alternatives" => ["custom-policy"], > "value-type" => { > "policy" => { > "type" => STRING, > "description" => "The name of a java.security.Policy implementation referencing a policy provider.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => "org.wildfly.security.authz.jacc.JaccDelegatingPolicy", > "min-length" => 1L, > "max-length" => 2147483647L > }, > "configuration-factory" => { > "type" => STRING, > "description" => "The name of a javax.security.jacc.PolicyConfigurationFactory implementation referencing a policy configuration factory provider.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "default" => "org.wildfly.security.authz.jacc.ElytronPolicyConfigurationFactory", > "min-length" => 1L, > "max-length" => 2147483647L > }, > "module" => { > "type" => STRING, > "description" => "The name of the module to load the provider from.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > "min-length" => 1L, > "max-length" => 2147483647L > } > }, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "no-services" > } > }, > "operations" => undefined, > "notifications" => undefined, > "children" => {} > } > }] > } > {code} > Firstly it only makes sense to have a single policy defined, the outcome of this resource is JVM wide registration so multiple definitions would lead to undefined behaviour. > Secondly this provides two primary functions. > 1. Instantation of https://docs.oracle.com/javase/8/docs/api/java/security/Policy.html and registration via a call to https://docs.oracle.com/javase/8/docs/api/java/security/Policy.html#setPo... > This first point needs a class name for the policy as well as a module. > 2. Registration of the JVM wide https://jakarta.ee/specifications/platform/8/apidocs/javax/security/jacc/... again needing a classname and module. > This is also not working correctly but the immediate bug is being addressed under WFCORE-5020 > The JACC APIs don't actually provide a nice way to register this so maybe this is something we should also propose via the spec, but this piece is effectively a class name and module name. > We have ended up with custom and jacc variants as alternatives. Really both variants are optional but if the resource is defined at least one must be set. > It may make sense for JACC to move to it's own subsystem for a couple of reasons. > The JVM wide policy will likely need to be possible in both subsystems but use a capability to ensure it is defined in only one. We probably should move it's registration into the boot operations so registration is complete before DUPs begin. > The PolicyConfigurationFactory would then be in a JACC subsystem only. Again handling during a boot operation may be preferable otherwise we see issues like WFLY-13615 but failing that ensuring the deployment depend upon the registration happening may be sufficient. > Additionally the resource has some hard coded class names for the Policy and PolicyConfigurationFactory, we probably should not have these as class names and instead default to them if not defined - this means we still need a way to optionally activate their registration if JACC is required on the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 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 July 2020