July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2563: -------------------------------- Epic Name: [DMN Editor] Add support to define data-types > [DMN Editor] Add support to define data-types > --------------------------------------------- > > Key: DROOLS-2563 > URL: https://issues.jboss.org/browse/DROOLS-2563 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > > As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type. > Verification conditions: > Support added for the User to define data-types ({{ItemDefinition}}). > This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2563: -------------------------------- Issue Type: Epic (was: Task) > [DMN Editor] Add support to define data-types > --------------------------------------------- > > Key: DROOLS-2563 > URL: https://issues.jboss.org/browse/DROOLS-2563 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > > As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type. > Verification conditions: > Support added for the User to define data-types ({{ItemDefinition}}). > This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1239) Elytron client, elytron-1_0.xsd, protection-parameter-credentials is incorrectly defined as client-credentials-type.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1239?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1239: ------------------------------------- Assignee: Justin Cook (was: Peter Skopek) > Elytron client, elytron-1_0.xsd, protection-parameter-credentials is incorrectly defined as client-credentials-type. > -------------------------------------------------------------------------------------------------------------------- > > Key: ELY-1239 > URL: https://issues.jboss.org/browse/ELY-1239 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Client, Credential Store > Reporter: Hynek Švábek > Assignee: Justin Cook > Priority: Blocker > Fix For: 1.4.1.CR1 > > > Elytron client, elytron-1_0.xsd, *protection-parameter-credentials* is incorrectly defined as client-credentials-type [1]. > For *protection-parameter-credentials* is valid only credential-store-reference element: > {code} > <xsd:element name="credential-store-reference" type="credential-store-reference-type"/> > {code} > But now is *protection-parameter-credentials* defined as type *client-credentials-type* [1] which can have these values: > {code} > <xsd:complexType name="client-credentials-type"> > <xsd:choice minOccurs="0" maxOccurs="unbounded"> > <xsd:element name="key-store-reference" type="key-store-ref-type"/> > <xsd:element name="credential-store-reference" type="credential-store-reference-type"/> > <xsd:element name="clear-password" type="clear-password-type"/> > <xsd:element name="hashed-password" type="hashed-password-type"/> > <xsd:element name="crypt-password" type="crypt-password-type"/> > <xsd:element name="key-pair" type="key-pair-type"/> > <xsd:element name="certificate" type="certificate-type"/> > <xsd:element name="public-key-pem" type="xsd:string"/> > <xsd:element name="bearer-token" type="bearer-token-type"/> > <xsd:element name="oauth2-bearer-token" type="oauth2-bearer-token-type"/> > </xsd:choice> > </xsd:complexType> > {code} > Please keep on mind that changes must be done accordingly in ElytronXMLParser too. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.1.0.Beta47/src... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1332) NSS tools based PKCS11 provider defined in Elytron doesn't survive server reload

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1332?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1332: ---------------------------------- Priority: Major (was: Blocker) > NSS tools based PKCS11 provider defined in Elytron doesn't survive server reload > -------------------------------------------------------------------------------- > > Key: ELY-1332 > URL: https://issues.jboss.org/browse/ELY-1332 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Fix For: 1.4.1.CR1 > > > When a SunPKCS11 provider is defined in Elytron subsystem on the top of NSS keystore (e.g. a FIPS one), then the server reload fails with "ProviderException: Secmod module already configured". > The server.log contains: > {noformat} > 08:12:56,073 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service org.wildfly.security.providers.nss: org.jboss.msc.service.StartException in service org.wildfly.security.providers.nss: java.lang.reflect.InvocationTargetException > at org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:224) > at org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:160) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at org.wildfly.extension.elytron.ProviderDefinitions$1$1.get(ProviderDefinitions.java:190) > ... 7 more > Caused by: java.security.ProviderException: Secmod module already configured > at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:276) > at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:107) > ... 12 more > .. > 08:12:56,140 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("provider-loader" => "nss") > ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.providers.nss" => "java.lang.reflect.InvocationTargetException > Caused by: java.lang.reflect.InvocationTargetException > Caused by: java.security.ProviderException: Secmod module already configured"}} > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-243) Ensure reference to repository is removed from pom

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-243?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-243: --------------------------------- Priority: Major (was: Blocker) > Ensure reference to repository is removed from pom > -------------------------------------------------- > > Key: ELY-243 > URL: https://issues.jboss.org/browse/ELY-243 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Fix For: 1.4.1.CR1 > > > We need to ensure the reference to the JBoss repo is removed from the pom and artefacts are available from Maven Central. > Also at this point probably good to put the steps in place for Elytron to also be available from Maven Central. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2563: ------------------------------------- [~jomarko] Anything that uplevels the parent issue sounds good to me. I'll try to get the planning poker thingy added, otherwise we can just vote in chat. > [DMN Editor] Add support to define data-types > --------------------------------------------- > > Key: DROOLS-2563 > URL: https://issues.jboss.org/browse/DROOLS-2563 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Carreiro > > As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type. > Verification conditions: > Support added for the User to define data-types ({{ItemDefinition}}). > This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10652) Mdb Clustered Singleton Delivery is not working

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-10652?page=com.atlassian.jira.plugin... ] Miroslav Novak reopened WFLY-10652: ----------------------------------- [~pferraro] Clustered Singleton MDB is still broken. Problem is that none of MDBs in cluster gets activate. I could reproduce it in quickstart as well. Here is reproducer: {code} git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout eap7.2.0.EO12 groovy -DEAP_ZIP_URL=https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/538//artifact/jboss-eap.zip PrepareServers7.groovy # it's Widfly master build - 1 day old export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn -Deap7.clients.version=7.1531249415-wildfly-master-SNAPSHOT clean install -B -Dtest=ClusteredSingletonMDBTestCase#clusterMDBSigletonTestDescriptorsShutdown {code} I'll reopen this jira. > Mdb Clustered Singleton Delivery is not working > ------------------------------------------------ > > Key: WFLY-10652 > URL: https://issues.jboss.org/browse/WFLY-10652 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Flavia Rainone > Assignee: Paul Ferraro > Fix For: 14.0.0.CR1 > > > When trying to deploy an application with clustered singleton MDB delivery, we see this error: > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.ejb3.clustered.singleton"],"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"messaging-clustering-singleton.war\".clustered.singleton.dependency is missing [org.wildfly.ejb3.clustered.singleton]"]}}} > The clustered singleton service is not being installed with the expected name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10692) ActiveCount of data-source is not correct after reload

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-10692?page=com.atlassian.jira.plugin... ] Tomas Hofman updated WFLY-10692: -------------------------------- Component/s: JCA > ActiveCount of data-source is not correct after reload > ------------------------------------------------------ > > Key: WFLY-10692 > URL: https://issues.jboss.org/browse/WFLY-10692 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > Sometimes PoolStatisticsImpl is cleared too late during AS reload, and some connections are already counted. That results in wrong stats count (e.g. "ActiveCount"). > See JBEAP-14635 for reproducer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1379) ActiveCount of data-source is not correct after reload

by Tomas Hofman (JIRA)

Tomas Hofman created JBJCA-1379: ----------------------------------- Summary: ActiveCount of data-source is not correct after reload Key: JBJCA-1379 URL: https://issues.jboss.org/browse/JBJCA-1379 Project: IronJacamar Issue Type: Bug Reporter: Tomas Hofman Assignee: Tomas Hofman Fix For: 2.0.0.CR1, 1.4.10 Sometimes PoolStatisticsImpl is cleared too late during AS reload, and some connections are already counted. That results in wrong stats count (e.g. "ActiveCount"). See JBEAP-14635 for reproducer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10692) ActiveCount of data-source is not correct after reload

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-10692?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBJCA-1379 to WFLY-10692: -------------------------------------------- Project: WildFly (was: IronJacamar) Key: WFLY-10692 (was: JBJCA-1379) Workflow: GIT Pull Request workflow (was: classic default workflow) Fix Version/s: (was: 2.0.0.CR1) (was: 1.4.10) > ActiveCount of data-source is not correct after reload > ------------------------------------------------------ > > Key: WFLY-10692 > URL: https://issues.jboss.org/browse/WFLY-10692 > Project: WildFly > Issue Type: Bug > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > Sometimes PoolStatisticsImpl is cleared too late during AS reload, and some connections are already counted. That results in wrong stats count (e.g. "ActiveCount"). > See JBEAP-14635 for reproducer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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