September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4471) Artifacts for revised DMN Data Type Editor UX design

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4471?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4471: -------------------------------------- Attachment: Screen Shot 2019-09-06 at 10.28.44 PM.png > Artifacts for revised DMN Data Type Editor UX design > ---------------------------------------------------- > > Key: DROOLS-4471 > URL: https://issues.jboss.org/browse/DROOLS-4471 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-09-06 at 10.28.44 PM.png > > > Create an updated wireframe click-thru to document the redesign of the Data Type editor based on usability study findings, as documented at: https://docs.google.com/presentation/d/10GZUd6oLaQohK27iJ1S6eF-WfvF8whXH5... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12511) Update community documentation for Jakarta EE 8

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12511?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12511: ------------------------------------- [https://github.com/wildfly/wildfly/pull/12604] > Update community documentation for Jakarta EE 8 > ----------------------------------------------- > > Key: WFLY-12511 > URL: https://issues.jboss.org/browse/WFLY-12511 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4630) Move to jakarta.inject:jakarta.inject-api

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4630?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4630: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3947 (was: https://github.com/wildfly/wildfly-core/pull/3946) > Move to jakarta.inject:jakarta.inject-api > ----------------------------------------- > > Key: WFCORE-4630 > URL: https://issues.jboss.org/browse/WFCORE-4630 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > Migrate from javax.inject:javax.inject:1 to jakarta.inject:jakarta.inject-api:1.0 once it has been formally released and available at maven central. > Jakarta specification release: https://github.com/jakartaee/specifications/pull/63 > WildFly boms would need to be revised. > WildFly feature-packs are also using the javax.inject:javax.inject dependency. > Exclusions for other dependencies could be required -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4648) Migrate javax.json to jakarta.json

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4648?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4648: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3947 (was: https://github.com/wildfly/wildfly-core/pull/3946) > Migrate javax.json to jakarta.json > ---------------------------------- > > Key: WFCORE-4648 > URL: https://issues.jboss.org/browse/WFCORE-4648 > Project: WildFly Core > Issue Type: Task > Components: Modules > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 10.0.0.Final > > > * Migrate {{javax.json:javax.json-api:1.1.2}} to {{jakarta.json:jakarta-json-api:1.1.6}}. > * Migrate {{org.glassfish:javax.json:1.1.2}} to {{org.glassfish:jakarta.json:1.1.6}} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4630) Move to jakarta.inject:jakarta.inject-api

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4630?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4630: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3946 > Move to jakarta.inject:jakarta.inject-api > ----------------------------------------- > > Key: WFCORE-4630 > URL: https://issues.jboss.org/browse/WFCORE-4630 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > > Migrate from javax.inject:javax.inject:1 to jakarta.inject:jakarta.inject-api:1.0 once it has been formally released and available at maven central. > Jakarta specification release: https://github.com/jakartaee/specifications/pull/63 > WildFly boms would need to be revised. > WildFly feature-packs are also using the javax.inject:javax.inject dependency. > Exclusions for other dependencies could be required -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12511) Update community documentation for Jakarta EE 8

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12511?page=com.atlassian.jira.plugin... ] Scott Marlow reassigned WFLY-12511: ----------------------------------- Assignee: Scott Marlow > Update community documentation for Jakarta EE 8 > ----------------------------------------------- > > Key: WFLY-12511 > URL: https://issues.jboss.org/browse/WFLY-12511 > Project: WildFly > Issue Type: Task > Components: Documentation > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2859) Treating all JAX-RS components as CDI Beans has some negative consequences

by Matt Drees (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Matt Drees commented on WFLY-2859: ---------------------------------- I verified my app finally boots just fine on wildfly 18.0.0.Beta1 without my previous workaround. Thanks Ronald, James, R, Marek and everyone else who has worked on this! > Treating all JAX-RS components as CDI Beans has some negative consequences > -------------------------------------------------------------------------- > > Key: WFLY-2859 > URL: https://issues.jboss.org/browse/WFLY-2859 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, REST > Affects Versions: 8.0.0.CR1, 16.0.0.Beta1 > Reporter: Matt Drees > Assignee: Ronald Sigal > Priority: Major > Fix For: 18.0.0.Beta1 > > > It seems that wildfly is now treating all jax-rs Providers and Resources as CDI Beans. This is probably fine most of the time, but there are some Provider classes that cause UnproxyableResolutionException (WELD-001437) errors, due to the fact that resteasy-cdi attempts to get bean reference whose type is identical to the bean class. > See the forum link for a specific instance of this. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3953: ------------------------------------------- [~danielezonca] [~karreiro] [~gabriolo] I got some feedback from [~tirelli] that the on-click approach might not be good for some of our business use cases. So I created an alternative on-hover solution. But to address the keyboard accessibility concerns that were raised I pulled the actions (copy, view alerts) out of the popover. Here's an updated click-thru: https://marvelapp.com/66j6fei > DMN UX - overlay validation error reporting > ------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png > > > As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table. > I want to see this kind of errors in the decisions and at diagram level. > * As a user I want to run a validation test within the DMN editor, using the Validate toolbar action, to be able to identify elements within the graph or grids that have errors, so that I can resolve the issues. > * As a user when I save a file (and it is validated) I want to be informed if there are any validation errors, so that I'm aware that there are issues that need to be resolved. > * As a user when I test a rule in the Scenario tool and any scenarios fail due to a syntax errors within DMN, I need to be able to easily identify the portions of the DMN file with errors so that I can fix them. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6008) CommandDispatcher commands execute using wrong TCCL

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-6008?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-6008: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12602 (was: https://github.com/wildfly/wildfly/pull/12597) > CommandDispatcher commands execute using wrong TCCL > --------------------------------------------------- > > Key: WFLY-6008 > URL: https://issues.jboss.org/browse/WFLY-6008 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.CR5 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > A command containing the following code: > {noformat} > public class MyCommand implements Command<Void, Void> { > public Void execute(Void context) throws Exception { > Thread.currentThread().getClassLoader().loadClass(this.getClass().getName()); > } > } > {noformat} > currently throws a ClassNotFoundException. > A command executed with the command dispatcher should be able to load application classes using the TCCL. > In fact, the following application callbacks from the clustering API all use the wrong TCCL: > * CommandDispatcher command execution > * CommandDispatcherFactory cluster membership listener > * Cache topology membership listener > * Registry listener > * ServiceProviderRegistry listener -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12477) CommandDispatcher commands cannot read application jndi namespace

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12477?page=com.atlassian.jira.plugin... ] Paul Ferraro updated WFLY-12477: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12602 (was: https://github.com/wildfly/wildfly/pull/12597) > CommandDispatcher commands cannot read application jndi namespace > ----------------------------------------------------------------- > > Key: WFLY-12477 > URL: https://issues.jboss.org/browse/WFLY-12477 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > A command containing the following code: > {noformat} > public class MyCommand implements Command<Void, Void> { > public Void execute(Void context) throws Exception { > new InitialContext().lookup("java:comp/env/existing-resource"); > } > } > {noformat} > currently throws a NameNotFoundException, even though the same JNDI lookup succeeds on the caller that invoked the command. > A command executed with the command dispatcher should be able to perform JNDI lookup from the local application namespace. > In fact, the following application callbacks from the clustering API are all unable to read from the application's JNDI namespace: > * CommandDispatcher command execution > * CommandDispatcherFactory cluster membership listener > * Cache topology membership listener > * Registry listener > * ServiceProviderRegistry listener -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 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 September 2019