February 2019 - jboss-jira - Jboss List Archives

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

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Marek Kopecký commented on WFLY-2859: ------------------------------------- This issue is still valid in WF16. > 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: Stuart Douglas > Priority: Major > > 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.12.1#712002)

7 years, 2 months

1
0
0 / 0

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

by Marek Kopecký (Jira)

[ https://issues.jboss.org/browse/WFLY-2859?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated WFLY-2859: -------------------------------- Affects Version/s: 16.0.0.Beta1 > 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: Stuart Douglas > Priority: Major > > 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.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3693) Prepare a crash course on how to use JP for parsing and generating code

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3693?page=com.atlassian.jira.plugi... ] Luca Molteni reassigned DROOLS-3693: ------------------------------------ Assignee: Luca Molteni (was: Mario Fusco) > Prepare a crash course on how to use JP for parsing and generating code > ----------------------------------------------------------------------- > > Key: DROOLS-3693 > URL: https://issues.jboss.org/browse/DROOLS-3693 > Project: Drools > Issue Type: Task > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3693) Prepare a crash course on how to use JP for parsing and generating code

by Luca Molteni (Jira)

Luca Molteni created DROOLS-3693: ------------------------------------ Summary: Prepare a crash course on how to use JP for parsing and generating code Key: DROOLS-3693 URL: https://issues.jboss.org/browse/DROOLS-3693 Project: Drools Issue Type: Task Reporter: Luca Molteni Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11768) Upgrade libthrift from 0.11.0 to 0.12.0

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFLY-11768?page=com.atlassian.jira.plugin... ] Jeff Mesnil updated WFLY-11768: ------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12109 (was: https://issues.jboss.org/browse/WFLY-11768) > Upgrade libthrift from 0.11.0 to 0.12.0 > --------------------------------------- > > Key: WFLY-11768 > URL: https://issues.jboss.org/browse/WFLY-11768 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenTracing > Reporter: James Perkins > Assignee: Jeff Mesnil > Priority: Major > > Upgrade {{org.apache.thrift:libthrift}} from 0.11.0 to 0.12.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3676) Create a generated Java Class Filed representing the structure of the KieModuleModel

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3676?page=com.atlassian.jira.plugi... ] Luca Molteni resolved DROOLS-3676. ---------------------------------- Resolution: Done > Create a generated Java Class Filed representing the structure of the KieModuleModel > ------------------------------------------------------------------------------------- > > Key: DROOLS-3676 > URL: https://issues.jboss.org/browse/DROOLS-3676 > Project: Drools > Issue Type: Feature Request > Environment: We need a way to represent the contents of the KieModuleModel without using reflection, therefore we should generate a class based on the content of the kmodule.xml file > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3577) Lightweight (jBPM) runtimeimpl (alternative to kiesession)

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3577?page=com.atlassian.jira.plugi... ] Edoardo Vacchi resolved DROOLS-3577. ------------------------------------ Resolution: Explained > Lightweight (jBPM) runtimeimpl (alternative to kiesession) > ---------------------------------------------------------- > > Key: DROOLS-3577 > URL: https://issues.jboss.org/browse/DROOLS-3577 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > This is an experimental, "investigation" task. The idea is to evaluate an approach to build a lightweight session substitute for jBPM > Other points to take into account: > - we should move some of the internals to standalone services. Not every runtimeimpl needs it's own instance of Calendars. WorkItemManager can probably be moved out too. > > - revisit how jBPM uses Drools. we need to make rule usage lightweight, so it's only a little harder than add a method; e.g. use canonical model directly etc -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2924) Factor out Unit behavior to allow pluggable backends

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-2924?page=com.atlassian.jira.plugi... ] Edoardo Vacchi closed DROOLS-2924. ---------------------------------- Resolution: Deferred A prototype PR has been completed and verified, but not merged. It will be superseded by ongoing work > Factor out Unit behavior to allow pluggable backends > ---------------------------------------------------- > > Key: DROOLS-2924 > URL: https://issues.jboss.org/browse/DROOLS-2924 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: Stunner, drools-core, ruleunits > > The way (Rule) units are scheduled into execution is ad-hoc for Rule Units. Assuming we want to generalize the "Unit" flow of execution to a global API, having e.g. > - rule units (Drools) > - process units (jBPM) > - etc. > then the mechanism must allow for extensions. > This tasks consists in implementing a more general "Scheduler" interface, to which units can be submitted. The scheduler decides which unit has to be run next, depending on which Units are "in scope" and the actions they perform (e.g., submitting new units for run()'ing, registering a guard, etc.) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports

by Roger Martínez (Jira)

[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ] Roger Martínez commented on DROOLS-3659: ---------------------------------------- Yeah [~uxdlc] it was [~tdolphine] who implemented the process documentation stuff :) (although you're always on our minds [~tfernand] don't be jealous :P ) > DMN: UX for documentation reports > --------------------------------- > > Key: DROOLS-3659 > URL: https://issues.jboss.org/browse/DROOLS-3659 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > User stories: > * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file. > * As a user I need a means through the UI to input additional documentation, links and attachments to nodes. > Notes: > - Docs to help with docs formatting. > - Might be able to leverage Case View docs widget. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11770) Force offline mode for provisioning

by Alexey Loubyansky (Jira)

[ https://issues.jboss.org/browse/WFLY-11770?page=com.atlassian.jira.plugin... ] Alexey Loubyansky updated WFLY-11770: ------------------------------------- Description: This does not really have any effect on our builds since all the artifacts are resolved locally anyway (either being produced by the build process or downloaded as project dependencies by maven). This setting is mostly to make sure that if one day Galleon attempts to download something from a remote repository, it will fail. (was: Purely to reduce the build time. Provisioning of the example configurations on average doubles the time (e.g. provisioning build dist with example configs took on my laptop 16 sec and 7 sec w/o the example configs). NOTE: the legacy build does include example configs, which means this will show up in diff comparing the two. If this is not desirable then this issue should be rejected.) > Force offline mode for provisioning > ----------------------------------- > > Key: WFLY-11770 > URL: https://issues.jboss.org/browse/WFLY-11770 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > Priority: Major > > This does not really have any effect on our builds since all the artifacts are resolved locally anyway (either being produced by the build process or downloaded as project dependencies by maven). This setting is mostly to make sure that if one day Galleon attempts to download something from a remote repository, it will fail. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 February 2019