March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4360) Support encrypted expression resolution using a CredentialStore

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4360?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4360: -------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Beta1) > Support encrypted expression resolution using a CredentialStore > --------------------------------------------------------------- > > Key: WFCORE-4360 > URL: https://issues.jboss.org/browse/WFCORE-4360 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 9.0.0.Beta2 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Matej Novotny (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Matej Novotny edited comment on WFLY-11858 at 3/20/19 9:22 AM: --------------------------------------------------------------- bq. Would you have some clue for me how to get info on all the registered beans (which can be `@Inject`ed?) Hmm, first thing coming to mind is a CDI extension with observer for container lifecycle events (such as bean addition - {{ProcessBean}}, or producer method etc). [{{ProcessBean}}|http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#process_bean] is probably a good starting point as it triggers for every added bean, no matter if it is backed by class/producer method or added synthetically. bq. To your point about `new IntialContext()` I think it's not an issue as it's practice used on many places in the container and second there should be possibly one `JNDIBean` in container(?, I can be easily missing how the CDI handles this). Those are both good points, you are right :-) was (Author: manovotn): bq. Would you have some clue for me how to get info on all the registered beans (which can be `@Inject`ed?) Hmm, first thing coming to mind is a CDI extension with observer for container lifecycle events (such as bean addition - {{ProcessBean}}, or producer method etc). {{ProcessBean}} is probably a good starting point as it triggers for every added mean, no matter if it is backed by class/producer method or added synthetically. bq. To your point about `new IntialContext()` I think it's not an issue as it's practice used on many places in the container and second there should be possibly one `JNDIBean` in container(?, I can be easily missing how the CDI handles this). Those are both good points, you are right :-) > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

by Matej Novotny (Jira)

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Matej Novotny commented on WFLY-11858: -------------------------------------- bq. Would you have some clue for me how to get info on all the registered beans (which can be `@Inject`ed?) Hmm, first thing coming to mind is a CDI extension with observer for container lifecycle events (such as bean addition - {{ProcessBean}}, or producer method etc). {{ProcessBean}} is probably a good starting point as it triggers for every added mean, no matter if it is backed by class/producer method or added synthetically. bq. To your point about `new IntialContext()` I think it's not an issue as it's practice used on many places in the container and second there should be possibly one `JNDIBean` in container(?, I can be easily missing how the CDI handles this). Those are both good points, you are right :-) > [Wildfly16] CDI fails to inject InitialContext during startup > ------------------------------------------------------------- > > Key: WFLY-11858 > URL: https://issues.jboss.org/browse/WFLY-11858 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Transactions > Affects Versions: 16.0.0.Final > Reporter: Rakesh K. Cherukuri > Assignee: Matej Novotny > Priority: Major > Attachments: stacktrace.log > > > We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error > _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_ > In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error. > Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself. > Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :) > Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-613) Document Manual Events

by Matt Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-613?page=com.atlassian.jira.plugin.... ] Matt Mahoney reassigned SWSQE-613: ---------------------------------- Assignee: Matt Mahoney > Document Manual Events > ---------------------- > > Key: SWSQE-613 > URL: https://issues.jboss.org/browse/SWSQE-613 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matt Mahoney > Assignee: Matt Mahoney > Priority: Major > Labels: infrastructure > > Document what can not be automated > Document why it can not be automated -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Gabriele Cardosi closed DROOLS-3608. ------------------------------------ Resolution: Done > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3783) Fix runner for top-level collection

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3783: ---------------------------------------- Summary: Fix runner for top-level collection Key: DROOLS-3783 URL: https://issues.jboss.org/browse/DROOLS-3783 Project: Drools Issue Type: Sub-task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Fix the runner for scenarios containing top-level collection -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3759) Extends editing support inside CollectionEditor

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3759?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3759: ------------------------------------- Parent: DROOLS-3782 Issue Type: Sub-task (was: Enhancement) > Extends editing support inside CollectionEditor > ----------------------------------------------- > > Key: DROOLS-3759 > URL: https://issues.jboss.org/browse/DROOLS-3759 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Attachments: 1.png > > > Currently the CollectionEditor does not allow to insert/edit "complex" properties (i.e. properties mapped to other bean/datatype) but only for "simple" ones (e.g. String, number, boolean). > It should be possible to *at least* insert/edit first-level complex properties > h3. Issues that need to be addressed as a part of this task: > # The top-level collections message inside the *Unsupported DMN asset* should no longer be displayed: > !1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3608: ------------------------------------- Parent: DROOLS-3782 Issue Type: Sub-task (was: Enhancement) > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3608) Wrong behavior with top level collection in DMN scenario

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3608?page=com.atlassian.jira.plugi... ] Gabriele Cardosi reopened DROOLS-3608: -------------------------------------- > Wrong behavior with top level collection in DMN scenario > -------------------------------------------------------- > > Key: DROOLS-3608 > URL: https://issues.jboss.org/browse/DROOLS-3608 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > Attachments: dmn-list.dmn > > > If you have a DMN file with a top level collection like a list of string not as field of a complex object but as top level. The type is not correctly loaded and managed. > Top-level collection should work also in Rule scenario. > See dmn-list.dmn as example -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3782) Enable top-level collection support

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-3782: ---------------------------------------- Summary: Enable top-level collection support Key: DROOLS-3782 URL: https://issues.jboss.org/browse/DROOLS-3782 Project: Drools Issue Type: Enhancement Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Enable top-level collection support for dmn scenarios. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 March 2019