August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2826) [DMN Designer] Unable to resolve type reference

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2826?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2826: ---------------------------------------- For the information of [~manstis]... this needs to be tested with ```drools-wb-webapp``` as it's the incremental build throwing the exception. Also, for the information of [~manstis] it's likely a change made to ```QName``` for DROOLS-2792 fixes this (the zero-argument constructor for ```QName``` changed....). > [DMN Designer] Unable to resolve type reference > ----------------------------------------------- > > Key: DROOLS-2826 > URL: https://issues.jboss.org/browse/DROOLS-2826 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: error.log > > > During saving (also deploying) non empty dmn model, the error about resolving type reference appears in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2826) [DMN Designer] Unable to resolve type reference

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2826?page=com.atlassian.jira.plugi... ] Michael Anstis edited comment on DROOLS-2826 at 8/2/18 5:09 PM: ---------------------------------------------------------------- For the information of [~manstis]... this needs to be tested with {{drools-wb-webapp}} as it's the incremental build throwing the exception. Also, for the information of [~manstis] it's likely a change made to {{QName}} for DROOLS-2792 fixes this (the zero-argument constructor for {{QName}} changed....). was (Author: manstis): For the information of [~manstis]... this needs to be tested with ```drools-wb-webapp``` as it's the incremental build throwing the exception. Also, for the information of [~manstis] it's likely a change made to ```QName``` for DROOLS-2792 fixes this (the zero-argument constructor for ```QName``` changed....). > [DMN Designer] Unable to resolve type reference > ----------------------------------------------- > > Key: DROOLS-2826 > URL: https://issues.jboss.org/browse/DROOLS-2826 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: error.log > > > During saving (also deploying) non empty dmn model, the error about resolving type reference appears in the server log. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2787: ---------------------------------------- Hi [~uxdlc], The User will be unable to create, edit or delete "simple" (built-in, default) data-types. IIUC the child probably is never the same as the parent and clearing the definition to reset the fields is perfect. > "Data Type" tree-grid table interactions. > ----------------------------------------- > > Key: DROOLS-2787 > URL: https://issues.jboss.org/browse/DROOLS-2787 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.) > * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.) > * *Remove* Data Types from the list of available selections. > * be prevented from making selections that are not valid or would cause an error. > * know that when I edit a data type the changes will be updated in the DMN model. > Functional considerations/ pre conditions: > * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10634) mod_cluster custom load metric classes are loaded from the subsystem classloader

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10634?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-10634: ---------------------------------- Description: The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong since there is no way to specify which module to use. We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). was: The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong. We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). > mod_cluster custom load metric classes are loaded from the subsystem classloader > -------------------------------------------------------------------------------- > > Key: WFLY-10634 > URL: https://issues.jboss.org/browse/WFLY-10634 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > The mod_cluster custom load metrics classes are loaded from the subsystem classloader which requires users to tinker with our module structure. This is wrong since there is no way to specify which module to use. > We should just expose {{module}} attribute on the custom load metric (defaults to current default which is mod_cluster module, so no compatibility issues). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10789) Upgrade Hibernate ORM to 5.3.4.Final, also Byte Buddy to 1.8.15

by Scott Marlow (JIRA)

Scott Marlow created WFLY-10789: ----------------------------------- Summary: Upgrade Hibernate ORM to 5.3.4.Final, also Byte Buddy to 1.8.15 Key: WFLY-10789 URL: https://issues.jboss.org/browse/WFLY-10789 Project: WildFly Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 14.0.0.CR1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2787: ------------------------------------- [~manstis] - I will remove the add Simple types example from the click thru, thanks. I might have misunderstood [~tirelli] comments, although they were in his PDF as well? Hmm. So if you don't need to Add them, can the user Edit or Delete them? If so, then I guess this master list would be pre-populated with the Simple types. If not, then this would be as you had said earlier only for Custom/Structured types. - Yes to the dropdown options. I think it would have to clear the definitions in order to reset the fields. The child wouldn't need to be the same as the parent would it? Because you could have either Custom or Structured children within a parent Structured type - is that true? Thanks > "Data Type" tree-grid table interactions. > ----------------------------------------- > > Key: DROOLS-2787 > URL: https://issues.jboss.org/browse/DROOLS-2787 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.) > * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.) > * *Remove* Data Types from the list of available selections. > * be prevented from making selections that are not valid or would cause an error. > * know that when I edit a data type the changes will be updated in the DMN model. > Functional considerations/ pre conditions: > * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2787) "Data Type" tree-grid table interactions.

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2787?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-2787: ---------------------------------------- [~uxdlc] Looking like we're getting there. However a few comments: I don't think the User will be able to add "Simple" types. These appear to be the "built in/default" types defined by the DMN Specification. I assume the "Select a type" [drop-down|https://redhat.invisionapp.com/share/YXNBM5PGE52#/screens/31233...] allows the User to select "Custom" or "Structured". I assume the User can change their selection when creating or editing a type and this would clear the definition. I assume the child "Select a type" [drop-down|https://redhat.invisionapp.com/share/YXNBM5PGE52#/screens/31233...] is the same as the outer/upper/parent "Select a type" drop-down. Otherwise looks good to me :-) > "Data Type" tree-grid table interactions. > ----------------------------------------- > > Key: DROOLS-2787 > URL: https://issues.jboss.org/browse/DROOLS-2787 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2738.bmpr, Manage1.png, Manage2.png, Screen Shot 2018-07-24 at 3.51.03 PM.png, Screen Shot 2018-07-27 at 11.48.34 AM.png, Screen Shot 2018-07-27 at 12.24.49 PM.png, Screen Shot 2018-07-27 at 12.27.13 PM.png, add_basic.png, treegrid.png, type_definitions.pdf > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > As a user I want to: > * *Edit* the list of Data Types, using the appropriate type considering the DMN model (eg: in the age line, we need to select "Numeric" in the combobox.) > * *Add* a new data type, which might be a nested or otherwise complex object as defined by the (ItemDefinition.) > * *Remove* Data Types from the list of available selections. > * be prevented from making selections that are not valid or would cause an error. > * know that when I edit a data type the changes will be updated in the DMN model. > Functional considerations/ pre conditions: > * Outside of simple view/select, Data Types list (and options) will be presented as a tree-grid within a modal dialog. Discussed in detail within Epic subtask for the same. > * Design needs to be consistent with Stunner and PF components, such as: https://www.patternfly.org/pattern-library/widgets/#treegrid-table > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2774) Select a data type from the DMN canvas

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2774?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2774: -------------------------------- Sprint: 2018 Week 30-32 > Select a data type from the DMN canvas > --------------------------------------- > > Key: DROOLS-2774 > URL: https://issues.jboss.org/browse/DROOLS-2774 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: select.png > > > *Background* > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to *select* a data type, from a list of available data types, so I can associate it with a DMN node. > * From the DMN canvas view - as a user I want a *means to* add a desired data type to the list of available data types. > * From the DMN canvas view - as a user I want a *means to* edit a desired data type from the list of available data types. > Functional considerations/ pre conditions: > * Actions will be offered or spawned from right dock properties panel. > * Design needs to be consistent with Stunner and PF components. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10770) HotRodPersistenceWebFailoverTestCase fails

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10770?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10770: -------------------------------------- The issues seems to be with {{org.infinispan.server:infinispan-server-build}} which would be considered a thin server. The defined modules use Maven artifact id's so not libraries are included in the download. Because of this jboss-modules will attempt to load a {{settings.xml}} file from {{System.getProperty("user.home") + "/.m2"}}. If this file does not exist or the user does not have the JBoss Nexus repository defined in their {{settings.xml}} the start of the Infinispan server will fail because {{org.jboss.openjdk-orb:openjdk-orb}} is not synched to Maven Central. We have 3 options: # Sync {{org.jboss.openjdk-orb:openjdk-orb}} (should likely be done regardless of which option we choose) # Ensure a property {{settings.xml}} is available # Use {{org.infinispan.server:infinispan-server-feature-pack}} and provision a server locally for the tests Really all 3 should likely be done. Options 1 and 3 are likely the easiest to started with. > HotRodPersistenceWebFailoverTestCase fails > ------------------------------------------ > > Key: WFLY-10770 > URL: https://issues.jboss.org/browse/WFLY-10770 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Tom Jenkinson > Assignee: Paul Ferraro > Priority: Critical > > This test HotRodPersistenceWebFailoverTestCase seems to fail more or less consistently for me on CI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5497) Add <distributable/> to shared-session-config schema

by tommaso borgato (JIRA)

[ https://issues.jboss.org/browse/WFLY-5497?page=com.atlassian.jira.plugin.... ] tommaso borgato updated WFLY-5497: ---------------------------------- Tester: tommaso borgato > Add <distributable/> to shared-session-config schema > ---------------------------------------------------- > > Key: WFLY-5497 > URL: https://issues.jboss.org/browse/WFLY-5497 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Web (Undertow) > Affects Versions: 10.0.0.CR2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Currently, the shared-session-config does not indicate whether a distributable or non-distributable session manager should be used. Consequently, we assign the session manager implementation based on the availability of the module providing the distributed implementation. Since the default infinispan web session configuration attempts to passivate sessions on shutdown, users will see NotSerializableExceptions on shutdown if they use non-serializable session attributes - even if their web applications do not define themselves as being <distributable/>. > To clarify this ambiguity, we should add a <distributable/> element (a la web.xml) to the shared-session-config schema to determine which session manager implementation to use. -- 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