July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9754) Global flag to supress transaction propagation for EJB clients inside of an server application

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-9754?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov reassigned WFLY-9754: ------------------------------------ Assignee: Fedor Gavrilov (was: David Lloyd) > Global flag to supress transaction propagation for EJB clients inside of an server application > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9754 > URL: https://issues.jboss.org/browse/WFLY-9754 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Environment: JEE application inside of WildFly using remote invocation to EJB's deployed in another WildFly instance > Reporter: Wolf-Dieter Fink > Assignee: Fedor Gavrilov > > The remote interface can be marked with an annotation to control transaction propagation with > org.jboss.ejb.client.annotation.ClientTransactionPolicy.* > This can be useful if the application need to ensure a specific Tx behaviour for this combination. > Remember the client does not know whether the server side is flagged to use Tx or not! > But there are different issues > - the Remote interface is polluted with WildFly specific annotations > consider the interface could be used in an environment without WildFly > - any call to the remote application should not propagate Tx context > - any call to a remote server should not propagate a Tx context > Consider former versions where able to control the Tx propagation by using JTA or JTS > To have more control for the application assembler or server administrator the transaction propagation should be controlled with deployment descriptor or server configuration. > possible solutions to disable the Tx propagation > - add a flag in ejb-client.xml application descriptor (affect this application) > - add a configuration for remote-outbound-connection (affect this connection including a possible cluster) > - add a configuration server wide (affect all remote outbound connections) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2771) Option to invoke a Decision Server on the kie-server

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2771: -------------------------------------- Summary: Option to invoke a Decision Server on the kie-server Key: DROOLS-2771 URL: https://issues.jboss.org/browse/DROOLS-2771 Project: Drools Issue Type: Feature Request Components: dmn engine, kie server Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2770) Edit issue in Guided Decision Tree

by Chaitanya Patel (JIRA)

Chaitanya Patel created DROOLS-2770: --------------------------------------- Summary: Edit issue in Guided Decision Tree Key: DROOLS-2770 URL: https://issues.jboss.org/browse/DROOLS-2770 Project: Drools Issue Type: Feature Request Reporter: Chaitanya Patel Assignee: Edson Tirelli Attachments: EditButtonDoesNotWork_DifferentTree.PNG, WorkingDecisionTreeWithEdit.PNG I have a working Decision Tree having a data object whose edit functionality works fine when we try to click on the circles. I want to add another Decision Tree for a different Data Object but when I try to edit the circles(root object/other objects) in this scenario, the edit functionality does not open a pop up. There is no java script error either. Now I try to add a different data object to the new decision tree but still the edit functionality does not work. I have moved this decision tree and data object to a different package as well as to a different project. But still the edit button does not open a pop-up. Neither the close(X) button or collapse button work for these circles. Attaching the snapshots where edit functionality of one decision tree works and it does not work for other. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10727) RESTEASY008200: JSON Binding deserialization error for valid JSON

by Guido Schmidt (JIRA)

Guido Schmidt created WFLY-10727: ------------------------------------ Summary: RESTEASY008200: JSON Binding deserialization error for valid JSON Key: WFLY-10727 URL: https://issues.jboss.org/browse/WFLY-10727 Project: WildFly Issue Type: Feature Request Components: EE Affects Versions: 13.0.0.Final Reporter: Guido Schmidt -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3973) Upgrade CLI to use aesh-extensions 1.6

by Jean-Francois Denise (JIRA)

Jean-Francois Denise created WFCORE-3973: -------------------------------------------- Summary: Upgrade CLI to use aesh-extensions 1.6 Key: WFCORE-3973 URL: https://issues.jboss.org/browse/WFCORE-3973 Project: WildFly Core Issue Type: Component Upgrade Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise An invalid dependency on javafx has been found in aesh-extension. It has been removed in aesh-extensions 1.6 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3962) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Rostislav Svoboda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3962?page=com.atlassian.jira.plugi... ] Rostislav Svoboda updated WFCORE-3962: -------------------------------------- Labels: Java11 blocker-WF14 (was: Java11) > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFCORE-3962 > URL: https://issues.jboss.org/browse/WFCORE-3962 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 6.0.0.Alpha3 > Reporter: Matej Novotny > Assignee: David Lloyd > Priority: Blocker > Labels: Java11, blocker-WF14 > > As per request, copying MODULES-372 to WFCORE as well. > Starting WFLY with JDK 11 using {{standalone.sh}} yields: > {code} > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > {code} > Output of {{java -version}}: > {code} > openjdk version "11-ea" 2018-09-25 > OpenJDK Runtime Environment 18.9 (build 11-ea+21) > OpenJDK 64-Bit Server VM 18.9 (build 11-ea+21, mixed mode) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)

by Stetson Robinson (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] Stetson Robinson commented on DROOLS-2706: ------------------------------------------ [~g.dey18], this task at this point is basically here to agree on a name for the Simulation Scenario asset and go with that for the asset list and everywhere else in Central. I'll start an email about this to get better group feedback, and then turn over to you from there. The team is not using the same name for this asset consistently, and everyone needs to get on the same page from this point. > New "Scenario Test" asset list option (UX) > ------------------------------------------ > > Key: DROOLS-2706 > URL: https://issues.jboss.org/browse/DROOLS-2706 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Gaurav Dey > Labels: UX, UXTeam > > As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor. > *Verification conditions:* > The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.) > Notes: > Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2706) New "Scenario Test" asset list option (UX)

by Stetson Robinson (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2706?page=com.atlassian.jira.plugi... ] Stetson Robinson reassigned DROOLS-2706: ---------------------------------------- Assignee: Gaurav Dey (was: Stetson Robinson) > New "Scenario Test" asset list option (UX) > ------------------------------------------ > > Key: DROOLS-2706 > URL: https://issues.jboss.org/browse/DROOLS-2706 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Gaurav Dey > Labels: UX, UXTeam > > As a practitioner - I want to be able to distinguish the new Scenario Test tool option, from the existing one, within the Asset list so that I can quickly/easily create a test using the new editor. > *Verification conditions:* > The new Scenario Test tool is distinguishable from the existing test tool within the asset list, through visual inspection by the user (no hover/click required.) > Notes: > Need a way to identify "experimental" tools from existing (to be deprecated?) tools. Solution might include distinct names for each, or parenthetical append (e.g. "experimental, beta, preview...) Or visual indicator, such as an icon, flag, etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1615) Support for masked passwords in client XML config

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1615: ------------------------------------- Summary: Support for masked passwords in client XML config Key: ELY-1615 URL: https://issues.jboss.org/browse/ELY-1615 Project: WildFly Elytron Issue Type: Task Reporter: David Lloyd Assignee: Jan Kalina Priority: Critical Fix For: 1.4.1.CR1 We need a way to support masked passwords in the auth configuration file, either as: * A dedicated masked-password-type XML type * Adding necessary fields to hashed-password-type * Adding a modular crypt format Needs to be supported anywhere passwords are allowed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2703) Create a DMN V&V documentation

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2703?page=com.atlassian.jira.plugi... ] Toni Rikkola resolved DROOLS-2703. ---------------------------------- Resolution: Done > Create a DMN V&V documentation > ------------------------------ > > Key: DROOLS-2703 > URL: https://issues.jboss.org/browse/DROOLS-2703 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Toni Rikkola > Assignee: Toni Rikkola > > Simple plan on what needs to be done and estimates on how much time everything takes. -- 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 July 2018