January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1946) DMN Editor

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1946?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-1946: ------------------------------------- [~manstis] Linking to a related UX design jira for this work. > DMN Editor > ---------- > > Key: DROOLS-1946 > URL: https://issues.jboss.org/browse/DROOLS-1946 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Labels: UX > Fix For: 7.6.0.Final > > > Place holder for all DMN Editor related activities -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2212) [DMN Editor] Relation and Invocation can not be saved

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2212?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2212: ---------------------------------------- [~jomarko] Please see https://github.com/manstis/kie-wb-common/commit/9a5e4c253697558b172c57271... I am thinking of moving my branch into ```kiegroup/kie-wb-common``` and submit things as PRs too.. [~jomarko] [~tari_manga] WDYT (re: move DMN to ```kiegroup``` now)? > [DMN Editor] Relation and Invocation can not be saved > ----------------------------------------------------- > > Key: DROOLS-2212 > URL: https://issues.jboss.org/browse/DROOLS-2212 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: error.log > > > Save operation in dmn editor throws an exception if the dmn diagram contains decision node holding relation or invocation context entry. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2212) [DMN Editor] Relation and Invocation can not be saved

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2212?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-2212. ------------------------------------ Resolution: Done > [DMN Editor] Relation and Invocation can not be saved > ----------------------------------------------------- > > Key: DROOLS-2212 > URL: https://issues.jboss.org/browse/DROOLS-2212 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: error.log > > > Save operation in dmn editor throws an exception if the dmn diagram contains decision node holding relation or invocation context entry. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9648) Restore ability to disable initial state transfer for replicated/distributed caches

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9648: ---------------------------------- Summary: Restore ability to disable initial state transfer for replicated/distributed caches Key: WFLY-9648 URL: https://issues.jboss.org/browse/WFLY-9648 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 11.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro {code:xml}<state-transfer mode="DISABLED|ACTIVE|PASSIVE"/>{code} * DISABLED = cache starts cold, initial state transfer disabled * ACTIVE = cache starts warm, where initial state transfer enabled, but cache is not available until complete * PASSIVE = cache starts cold, but initial state transfer enabled -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3447) CLI security commands.

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3447?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3447: ----------------------------------------- Description: In order to help configure server side security, a set of CLI commands should be defined to drive users to realise the main use cases: - SSL keystore management - SSL/HTTPS enablement/disablement - SASL/HTTP authentication (based on certificate). Analysis docs, work in progress: https://developer.jboss.org/wiki/SSLCommandsForCLI and https://developer.jboss.org/wiki/AuthenticationCommandsForCLI was: In order to help configure server side security, a set of CLI commands should be defined to drive users to realise the main use cases: - SSL keystore management - SSL/HTTPS enablement/disablement - SASL/HTTP authentication (based on certificate). An analysis doc, work in progress: https://developer.jboss.org/wiki/SSLCommandsForCLI > CLI security commands. > ---------------------- > > Key: WFCORE-3447 > URL: https://issues.jboss.org/browse/WFCORE-3447 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > In order to help configure server side security, a set of CLI commands should be defined to drive users to realise the main use cases: > - SSL keystore management > - SSL/HTTPS enablement/disablement > - SASL/HTTP authentication (based on certificate). > Analysis docs, work in progress: https://developer.jboss.org/wiki/SSLCommandsForCLI and https://developer.jboss.org/wiki/AuthenticationCommandsForCLI -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9509) Default SFSB Lifecycle methods transaction attribute causing warnings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9509?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-9509: ----------------------------------------------- Jiří Bílek <jbilek(a)redhat.com> changed the Status of [bug 1508105|https://bugzilla.redhat.com/show_bug.cgi?id=1508105] from ON_QA to VERIFIED > Default SFSB Lifecycle methods transaction attribute causing warnings > --------------------------------------------------------------------- > > Key: WFLY-9509 > URL: https://issues.jboss.org/browse/WFLY-9509 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 12.0.0.Alpha1 > > Attachments: warning-reproducer.zip > > > EJB 2 deployment that does not specify transaction attribute for lifecycle methods such as: ejbActivate, ejbRemove, ejbPassivate are logging this warning. > JBAS014279: Invalid transaction attribute type REQUIRED on SFSB lifecyle method Method ejbRemove(), valid types are REQUIRES_NEW and NOT_SUPPORTED. Method will be treated as NOT_SUPPORTED. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-85) Support GSS-Proxy

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-85?page=com.atlassian.jira.plugin.sys... ] David Lloyd commented on ELY-85: -------------------------------- Does this work on IBM? > Support GSS-Proxy > ----------------- > > Key: ELY-85 > URL: https://issues.jboss.org/browse/ELY-85 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SASL > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Fix For: 1.2.0.Beta13 > > > GSS Proxy is something we should consider being able to support when running on an OS that supports it: - > -https://fedorahosted.org/gss-proxy/- > https://pagure.io/gssproxy > The big first step will be to identify what is required to achieve this, is this something that can be solved with a custom login module or does this also impact on the Java supplied GSSAPI implementation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1298) GssapiCompatibilitySuiteChild fails on IBM JDK

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1298?page=com.atlassian.jira.plugin.s... ] Jan Kalina reassigned ELY-1298: ------------------------------- Assignee: Jan Kalina > GssapiCompatibilitySuiteChild fails on IBM JDK > ---------------------------------------------- > > Key: ELY-1298 > URL: https://issues.jboss.org/browse/ELY-1298 > Project: WildFly Elytron > Issue Type: Bug > Components: Testsuite > Reporter: Peter Palaga > Assignee: Jan Kalina > Priority: Critical > Labels: ibm-java > > A followup of ELY-1293 > {{System.currentTimeMillis()}} is native in IBM JDK and at the same time, IBM JDK does not support java.lang.instrument API for native methods. Therefore, {{System.currentTimeMillis()}} cannot be mocked on IBM JDK using jmockit. > {code} > export JAVA_HOME=path/to/ibm/java8 > $JAVA_HOME/bin/java -version > java version "1.8.0" > Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12)) > IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled) > J9VM - R28_Java8_SR3_20160915_0912_B318796 > JIT - tr.r14.java.green_20160818_122998 > GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS > J9CL - 20160915_318796) > JCL - 20160914_01 based on Oracle jdk8u101-b13 > mvn clean test > {code} > Expected: the tests mocking {{System.currentTimeMillis()}} should pass > Actual: the tests mocking {{System.currentTimeMillis()}} throw the following exception or similar: > {code} > java.lang.UnsupportedOperationException: class redefinition failed: attempted to change method modifiers > at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest$1.<init>(PeriodicRotatingFileAuditEndpointTest.java:212) > at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest.mockTime(PeriodicRotatingFileAuditEndpointTest.java:212) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.lang.reflect.Method.invoke(Method.java:508) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) > {code} > This is currently the case with > * GssapiCompatibilitySuiteChild -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2212) [DMN Editor] Relation and Invocation can not be saved

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2212?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2212: ----------------------------------- Sprint: 2018 Week 01-02 > [DMN Editor] Relation and Invocation can not be saved > ----------------------------------------------------- > > Key: DROOLS-2212 > URL: https://issues.jboss.org/browse/DROOLS-2212 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Attachments: error.log > > > Save operation in dmn editor throws an exception if the dmn diagram contains decision node holding relation or invocation context entry. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-483) GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-483?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reassigned ELY-483: ------------------------------ Assignee: Jan Kalina > GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK > ---------------------------------------------------------------------------------------------------- > > Key: ELY-483 > URL: https://issues.jboss.org/browse/ELY-483 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta5 > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Labels: ibm-java > > Test cases initialization from GssapiTestSuite and Gs2Test fail with following exception for IBM JDK: > {code} > javax.security.auth.login.FailedLoginException: > Login error: com.ibm.security.krb5.KrbException, status code: 9 > message: The client or server has a null key > at com.ibm.security.jgss.i18n.I18NException.throwFailedLoginException(I18NException.java:15) > at com.ibm.security.auth.module.Krb5LoginModule.j(Krb5LoginModule.java:727) > at com.ibm.security.auth.module.Krb5LoginModule.b(Krb5LoginModule.java:307) > at com.ibm.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:59) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:507) > at javax.security.auth.login.LoginContext.invoke(LoginContext.java:788) > at javax.security.auth.login.LoginContext.access$000(LoginContext.java:196) > at javax.security.auth.login.LoginContext$5.run(LoginContext.java:721) > at javax.security.auth.login.LoginContext$5.run(LoginContext.java:719) > at java.security.AccessController.doPrivileged(AccessController.java:686) > at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:719) > at javax.security.auth.login.LoginContext.login(LoginContext.java:593) > at org.wildfly.security.sasl.gssapi.JaasUtil.login(JaasUtil.java:71) > at org.wildfly.security.sasl.gssapi.JaasUtil.loginClient(JaasUtil.java:53) > at org.wildfly.security.sasl.gssapi.JdkClientJdkServer.initialise(JdkClientJdkServer.java:47) > ... > {code} > It is test case issue but it can hide any another functional issue because affected tests are not running with IBM JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 January 2018