July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2744) [DMN Designer] Global diagram properties

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2744?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2744: ----------------------------------- Sprint: 2018 Week 27-29 > [DMN Designer] Global diagram properties > ---------------------------------------- > > Key: DROOLS-2744 > URL: https://issues.jboss.org/browse/DROOLS-2744 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The global diagram properties for DMN diagram contains sections settings for: > - dimensions > - backround > - font > However change of any of them (globally, for the whole diagram) doesn't seem to affect particular nodes somehow. We should hide these settings or implement the logic that would affect all nodes in diagram by change on this place. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] Rostislav Svoboda commented on WFCORE-3962: ------------------------------------------- {code} Java HotSpot(TM) 64-Bit Server VM warning: Ignoring system property options whose names match the '-Djdk.module.*'. names that are reserved for internal use. org.jboss.modules.ModuleNotFoundException: java.se at org.jboss.modules.Module.addPaths(Module.java:1266) at org.jboss.modules.Module.link(Module.java:1622) at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) at org.jboss.modules.Main.main(Main.java:437) {code} Using JAVA_OPTS="-server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djdk.module.addmods.0=java.se" dist/target/wildfly-14.0.0.Beta1-SNAPSHOT/bin/standalone.sh > Starting WFLY with JDK 11 blows up with ModuleNotFoundException java.se > ----------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 6.0.0.Alpha3 > Reporter: Matej Novotny > Assignee: David Lloyd > Priority: Blocker > Labels: Java11 > > As per request, copying MODULES-372 to WFCORE as well. > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1611) Document BEARER Token Mechanism and Token Realm

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-1611?page=com.atlassian.jira.plugin.s... ] Pedro Igor updated ELY-1611: ---------------------------- Issue Type: Enhancement (was: Bug) > Document BEARER Token Mechanism and Token Realm > ----------------------------------------------- > > Key: ELY-1611 > URL: https://issues.jboss.org/browse/ELY-1611 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Documentation, HTTP, Realms > Affects Versions: 1.4.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > Document BEARER HTTP mechanism and Token Realm in order to help people to understand the functionality and behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10719) Document BEARER Token Mechanism and Token Realm

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFLY-10719?page=com.atlassian.jira.plugin... ] Pedro Igor moved ELY-1612 to WFLY-10719: ---------------------------------------- Project: WildFly (was: WildFly Elytron) Key: WFLY-10719 (was: ELY-1612) Issue Type: Enhancement (was: Bug) Component/s: Documentation Security (was: Documentation) (was: HTTP) (was: Realms) Affects Version/s: 13.0.0.Final (was: 1.4.0.Final) > Document BEARER Token Mechanism and Token Realm > ----------------------------------------------- > > Key: WFLY-10719 > URL: https://issues.jboss.org/browse/WFLY-10719 > Project: WildFly > Issue Type: Enhancement > Components: Documentation, Security > Affects Versions: 13.0.0.Final > Reporter: Pedro Igor > Assignee: Pedro Igor > > Document BEARER HTTP mechanism and Token Realm in order to help people to understand the functionality and behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ELY-1612) Document BEARER Token Mechanism and Token Realm

by Pedro Igor (JIRA)

Pedro Igor created ELY-1612: ------------------------------- Summary: Document BEARER Token Mechanism and Token Realm Key: ELY-1612 URL: https://issues.jboss.org/browse/ELY-1612 Project: WildFly Elytron Issue Type: Bug Components: Documentation, HTTP, Realms Affects Versions: 1.4.0.Final Reporter: Pedro Igor Assignee: Pedro Igor Document BEARER HTTP mechanism and Token Realm in order to help people to understand the functionality and behavior. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10713) Can't build WF master with Java 11-ea+22

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10713?page=com.atlassian.jira.plugin... ] Rostislav Svoboda commented on WFLY-10713: ------------------------------------------ Just for the reference: https://github.com/wildfly/galleon-plugins/commit/52392e923fef18a24c0aa12... > Can't build WF master with Java 11-ea+22 > ---------------------------------------- > > Key: WFLY-10713 > URL: https://issues.jboss.org/browse/WFLY-10713 > Project: WildFly > Issue Type: Bug > Components: Build System > Reporter: Rostislav Svoboda > Assignee: Alexey Loubyansky > Priority: Critical > > Can't build WF master with 11-ea+22 > {code} > [INFO] WildFly: Servlet Galleon Pack ...................... FAILURE [ 3.481 s] > [ERROR] Failed to execute goal org.wildfly.galleon-plugins:wildfly-galleon-maven-plugin: > 2.0.0.Alpha4:generate-feature-specs > (feature-spec-build) on project wildfly-servlet-galleon-pack: > Feature spec generator failed: Forked embedded process has failed -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3967) Upgrade to Galleon and WildFly Galleon Plugins 2.0.0.Alpha4

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3967?page=com.atlassian.jira.plugi... ] Alexey Loubyansky commented on WFCORE-3967: ------------------------------------------- I added an upgrade to WildFly Galleon Plugins 2.0.0.Alpha5 in the PR to be able to build Core on JDK 11 (the reason it would fail otherwise is WFCORE-3962) > Upgrade to Galleon and WildFly Galleon Plugins 2.0.0.Alpha4 > ----------------------------------------------------------- > > Key: WFCORE-3967 > URL: https://issues.jboss.org/browse/WFCORE-3967 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Galleon 2.x is the version branch which is going to be exposed as a supported external tool for provisioning, updates and patching. > The main difference to Galleon 1.x that it brings into WildFly build process is it is based on different format for expressing feature-pack locations than Maven coordinates and uses a resolution mechanism to resolve feature-pack artifacts, which is the base for version updates and patches discovery. > There is still a way to provide Maven coordinates for feature-packs and avoid going through the default feature-pack resolution mechanism. > Another feature it brings in and which appears in wildfly feature-pack configs is proper transitive dependency customizations. > The equivalent change for WFLY is WFLY-10703 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2765) [DMN Designer] Exception in read only session

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2765?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2765: ---------------------------------------- [~jomarko] It is not related to DROOLS-2741. > [DMN Designer] Exception in read only session > --------------------------------------------- > > Key: DROOLS-2765 > URL: https://issues.jboss.org/browse/DROOLS-2765 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-07-19 13-32-53.png > > > There occurs a {{JavaScriptException}} if user enters a read only session during an expression editor is shown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2765) [DMN Designer] Exception in read only session

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2765?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2765: ---------------------------------------- [~jomarko] This is a new issue relating to version selection with the DMN Editor (when in "grid" view). Whenever a version is selected the state of the UI needs restoring to "graph" view before the new version is opened. > [DMN Designer] Exception in read only session > --------------------------------------------- > > Key: DROOLS-2765 > URL: https://issues.jboss.org/browse/DROOLS-2765 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Attachments: Screenshot from 2018-07-19 13-32-53.png > > > There occurs a {{JavaScriptException}} if user enters a read only session during an expression editor is shown. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7085) Server should verify EJB business methods during deployment and log a warning

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7085?page=com.atlassian.jira.plugin.... ] Romain Pelisse updated WFLY-7085: --------------------------------- Summary: Server should verify EJB business methods during deployment and log a warning (was: Server should verify EJB business methods during deployment and reject) > Server should verify EJB business methods during deployment and log a warning > ----------------------------------------------------------------------------- > > Key: WFLY-7085 > URL: https://issues.jboss.org/browse/WFLY-7085 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Romain Pelisse > Labels: downstream_dependency > Fix For: 12.0.0.Beta1, 12.0.0.Final, 13.0.0.Beta1, 13.0.0.Final > > > The ejb 3.2 core specification state in chapter 4.9.6 that business methods should not be declared as final or static. > But a Bean with a business method declared in the local or remote interface can be correct deployed and is accesible under some circumstances. > To ensure that the Bean is according to the spec and avoid runtime or injection issues the methods should be checked and a VerifyError should be thrown at deployment time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 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 July 2018