August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2890: ----------------------------------- Priority: Major (was: Blocker) > [DMN Designer] DMNDiagram properties > ------------------------------------ > > Key: DROOLS-2890 > URL: https://issues.jboss.org/browse/DROOLS-2890 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Fix For: 7.10.0.Final > > > If the project contains multiple dmn models, it can not be built. > h3. Manual acceptance test > - Prepare three models > -- Empty > -- Just graph nodes > -- Login inside graph nodes > - Check Deployment successful (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2890: ----------------------------------- Issue Type: Enhancement (was: Bug) > [DMN Designer] DMNDiagram properties > ------------------------------------ > > Key: DROOLS-2890 > URL: https://issues.jboss.org/browse/DROOLS-2890 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Labels: drools-tools > Fix For: 7.10.0.Final > > > If the project contains multiple dmn models, it can not be built. > h3. Manual acceptance test > - Prepare three models > -- Empty > -- Just graph nodes > -- Login inside graph nodes > - Check Deployment successful (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4028) Upgrade WildFly Elytron 1.5.4.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4028?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4028: -------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Upgrade WildFly Elytron 1.5.4.Final > ----------------------------------- > > Key: WFCORE-4028 > URL: https://issues.jboss.org/browse/WFCORE-4028 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 6.0.0.Beta2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4022) The key-store obtain-certificate operation currently fails with "Parameter 'type' may not be null"

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4022?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4022: -------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > The key-store obtain-certificate operation currently fails with "Parameter 'type' may not be null" > -------------------------------------------------------------------------------------------------- > > Key: WFCORE-4022 > URL: https://issues.jboss.org/browse/WFCORE-4022 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 6.0.0.Beta2 > > > Currently, executing the {{key-store}} {{obtain-certificate}} operation results in: > {code} > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "Parameter 'type' may not be null", > "response-headers" => {"process-state" => "reload-required"}, > "rolled-back" => true > } > {code} > This is due to a recent Let's Encrypt change where a new challenge type was introduced but not officially added to the ACME v2 protocol spec yet. The {{WildFlyAcmeClient}} only needs to be able to handle the "http-01" challenge type but should be able to handle being presented with many challenge options. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4002) Some security tests fail on closed channel exception

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-4002?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4002: -------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Some security tests fail on closed channel exception > ---------------------------------------------------- > > Key: WFCORE-4002 > URL: https://issues.jboss.org/browse/WFCORE-4002 > Project: WildFly Core > Issue Type: Bug > Components: Security, Test Suite > Affects Versions: 6.0.0.Alpha5 > Reporter: Richard Opalka > Assignee: Jan Kalina > Priority: Blocker > Labels: jdk11 > Fix For: 6.0.0.Beta2 > > > With latest JDK11 (build 11-ea+25) the following tests fail due to closed channel exception: > * domain-management/src/test/java/org/jboss/as/domain/management/security/auditlog/AuditLogHandlerBootEnabledTestCase.java > * testsuite/domain/src/test/java/org/jboss/as/test/integration/domain/HTTPSManagementInterfaceTestCase.java > * testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/KerberosNativeMgmtSaslTestCase.java > * testsuite/elytron/src/test/java/org/wildfly/test/integration/elytron/sasl/mgmt/ScramPlusMgmtSaslTestCase.java > * testsuite/manualmode/src/test/java/org/wildfly/core/test/standalone/mgmt/HTTPSManagementInterfaceTestCase.java > Is there a known SSL issue in JDK11? Could somebody from our security team investigate this issue? > When these tests will start passing WFCORE test suite will be passing 100% of tests on JDK11. > Potential investigator from our security team may want to include this PR: > https://github.com/wildfly/wildfly-core/pull/3420 > to fix known JDK11 issues. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Michael Anstis (JIRA)

Michael Anstis created DROOLS-2890: -------------------------------------- Summary: [DMN Designer] DMNDiagram properties Key: DROOLS-2890 URL: https://issues.jboss.org/browse/DROOLS-2890 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.10.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Blocker Fix For: 7.10.0.Final If the project contains multiple dmn models, it can not be built. h3. Manual acceptance test - Prepare three models -- Empty -- Just graph nodes -- Login inside graph nodes - Check Deployment successful (/) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2522: ----------------------------------- Summary: [DMN Designer] Palette aesthetics (was: [DMN Designer] Palette css style) > [DMN Designer] Palette aesthetics > --------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: UX, UXTeam > Attachments: palette.png > > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette css style

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2522: ---------------------------------------- [~tirelli] Absolutely! This JIRA is for me to align the code for DMN's palette with Process Designer's palette; which should make it look identical to the latter (re: spacing, padding, backgrounds etc). You also expressed a preference for the line widths of the icons themselves to be slimmer. This is something [~bdellasc] can handle for us; and [~uxdlc] has made a new JIRA (DROOLS-2887) for Brian to register his work against. > [DMN Designer] Palette css style > -------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: UX, UXTeam > Attachments: palette.png > > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9516) JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9516?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9516: ------------------------------------ Option #4, introduce lazy starting of the persistence unit (EntityManagerFactory) on first use of EM or EMF. Obviously, bytecode enhancement would not work and there would be an application delay waiting for the persistence unit deployment to complete. Perhaps some other things would also not work, but since not everything can work together, this might help some users. It could also reduce memory usage, in that unused persistent units wouldn't be deployed. > JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9516 > URL: https://issues.jboss.org/browse/WFLY-9516 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > Assignee: Scott Marlow > > If an ear contains two EJB sub deployments which each contain a Persistence Unit and a Stateless EJB which injects the PU that is in its jar using @PersistenceContext. There is a dependency being added where in the Stateless EJB from one deployment depends on the PU from the other jar. It appears this is happening after this bug fix WFLY-1531 > {code} > app.ear > - ejb-with-pu1.jar > - ejb-with-pu2.jar > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1639) FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1639?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1639: ---------------------------- Comment: was deleted (was: Looks like I can also reproduce this with Elytron 1.5.2.Final, i.e., before the fix for ELY-1622.) > FIPS PKCS11 Client side: only SunJSSE KeyManagers may be used > ------------------------------------------------------------- > > Key: ELY-1639 > URL: https://issues.jboss.org/browse/ELY-1639 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Blocker > > Fix of ELY-1622 introduced regression. It is not possible to do 1 way ssl (no key-store-ssl-certificate in wildfly-config.xml) with exception > {code} > 14:13:56,143 ERROR [org.jboss.as.cli.impl.CliLauncher] Error processing CLI: org.jboss.as.cli.CliInitializationException: Failed to connect to the controller > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:330) > at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:291) > at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:45) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > Caused by: org.jboss.as.cli.CommandLineException: Failed to resolve host 'localhost' > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1256) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1203) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1198) > at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:328) > ... 5 more > Caused by: java.io.IOException: Failed to obtain SSLContext > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:156) > at org.jboss.as.cli.impl.ModelControllerClientFactory$2.getClient(ModelControllerClientFactory.java:85) > at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1222) > ... 8 more > Caused by: java.security.KeyManagementException: FIPS mode: only SunJSSE KeyManagers may be used > at sun.security.ssl.SSLContextImpl.chooseKeyManager(SSLContextImpl.java:149) > at sun.security.ssl.SSLContextImpl.engineInit(SSLContextImpl.java:66) > at javax.net.ssl.SSLContext.init(SSLContext.java:282) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:372) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:221) > at org.wildfly.security.auth.client.AuthenticationContextConfigurationClient.getSSLContext(AuthenticationContextConfigurationClient.java:208) > at org.jboss.as.cli.impl.CLIModelControllerClient.<init>(CLIModelControllerClient.java:153) > ... 10 more > {code} > It is because after fix Fix of ELY-1622 custom keymanager is used. But it is forbidden by jdk FIPS PKCS11. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018