[JBoss JIRA] (LOGMGR-124) Add marker support
by Andreas Liebscher (Jira)
[ https://issues.jboss.org/browse/LOGMGR-124?page=com.atlassian.jira.plugin... ]
Andreas Liebscher commented on LOGMGR-124:
------------------------------------------
Any news on that?
Is it possible to exchange the Logger implementation in WildFly 17?
Logback would be fine.
> Add marker support
> ------------------
>
> Key: LOGMGR-124
> URL: https://issues.jboss.org/browse/LOGMGR-124
> Project: JBoss Log Manager
> Issue Type: Feature Request
> Components: core
> Affects Versions: 2.0.2.Final
> Reporter: Rob Heine
> Priority: Optional
>
> The logging engine currently (talking about the one included in WF-9) does not support Markers (like in implementations like "logback" and/or "log4j2").
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.
by Elizabeth Clayton (Jira)
Elizabeth Clayton created DROOLS-4574:
-----------------------------------------
Summary: Scenario test: UX to add an expression-based value.
Key: DROOLS-4574
URL: https://issues.jboss.org/browse/DROOLS-4574
Project: Drools
Issue Type: Story
Components: Scenario Simulation and Testing
Reporter: Elizabeth Clayton
Assignee: Elizabeth Clayton
As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-1941) [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target"
by Daniel José dos Santos (Jira)
[ https://issues.jboss.org/browse/DROOLS-1941?page=com.atlassian.jira.plugi... ]
Daniel José dos Santos reassigned DROOLS-1941:
----------------------------------------------
Assignee: Daniel José dos Santos (was: Michael Anstis)
> [DMN Editor] ToolBox: Add support for creating "source" nodes from a "target"
> -----------------------------------------------------------------------------
>
> Key: DROOLS-1941
> URL: https://issues.jboss.org/browse/DROOLS-1941
> Project: Drools
> Issue Type: Enhancement
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> The "Toolbox" (see {{DMNFlowActionsToolboxControlProvider}}) currently supports creating "target" nodes from a "source" node and automatically joining "source" to "target" however [~tirelli] has requested the ability to select an existing "target" node and create a new "source" node from the Toolbox with the resulting connector joining "source" to "target". I.E. support creating the inverse of what is currently supported.
> * Should be able to create a BKM from Decision (connection from BKM to Decision). At the moment you can select BKM and add Decision, but need to support selecting a Decision and making an incoming BKM
> * Should be able to create a KnowledgeSources from bothh Decisions and BKMs. At the moment you can select a KnowledgeSource and adda Decision or BKM, but need to support selecting either a Decision or BKM and making an incoming KS
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12600) Enabling org.remote.tests for EAT
by Panagiotis Sotiropoulos (Jira)
Panagiotis Sotiropoulos created WFLY-12600:
----------------------------------------------
Summary: Enabling org.remote.tests for EAT
Key: WFLY-12600
URL: https://issues.jboss.org/browse/WFLY-12600
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Panagiotis Sotiropoulos
Assignee: Panagiotis Sotiropoulos
Enable org.remote.tests from remote repositories.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12537) Incoming RunAsPrincipal is not being propagated to an unsecured EJB
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/WFLY-12537?page=com.atlassian.jira.plugin... ]
Darran Lofthouse updated WFLY-12537:
------------------------------------
Fix Version/s: 19.0.0.Beta1
> Incoming RunAsPrincipal is not being propagated to an unsecured EJB
> -------------------------------------------------------------------
>
> Key: WFLY-12537
> URL: https://issues.jboss.org/browse/WFLY-12537
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Diana Vilkolakova
> Assignee: Diana Vilkolakova
> Priority: Major
> Fix For: 19.0.0.Beta1
>
>
> This is a follow-up on WFLY-11604. When Elytron is activated, run-as-principal identity is not being propagated the same way it was for legacy. For JBEAP-9744, we updated EJBContext.getCallerPrincipal() so that when called from an unsecured bean with no incoming runas identity, an `anonymous` principal will be returned. The issue WFLY-11604 discovered that EJBContext.getCallerPrincipal is returning 'anonymous' when called on an unsecured EJB even when incoming RunAsPrincipal identity should have been propagated. This issue is to see whether this can be fixed without breaking the fix for JBEAP-9744.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-12599) Add tests for Metrics tags
by Rostislav Svoboda (Jira)
Rostislav Svoboda created WFLY-12599:
----------------------------------------
Summary: Add tests for Metrics tags
Key: WFLY-12599
URL: https://issues.jboss.org/browse/WFLY-12599
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Rostislav Svoboda
Assignee: Rostislav Svoboda
Since MicroProfile Metrics 2.0 it’s possible to assign tags to specific metrics using the API.
Add tests to ensure MP Metrics tags are working.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-4518) Implement UX styles for Test Coverage Report
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-4518?page=com.atlassian.jira.plugi... ]
Yeser Amer updated DROOLS-4518:
-------------------------------
Priority: Minor (was: Major)
> Implement UX styles for Test Coverage Report
> --------------------------------------------
>
> Key: DROOLS-4518
> URL: https://issues.jboss.org/browse/DROOLS-4518
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Elizabeth Clayton
> Assignee: Yeser Amer
> Priority: Minor
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Screen Shot 2019-09-10 at 9.35.23 AM.png, Screen Shot 2019-09-10 at 9.37.02 AM.png, Screenshot from 2019-09-10 17-52-00.png, Screenshot from 2019-09-20 12-30-01.png, Screenshot from 2019-09-20 16-05-04.png, Screenshot from 2019-09-20 16-10-22.png, screenshot-1.png
>
>
> The implemented styles for the Test Coverage Report panel do not align with the HTML/CSS provided in jira https://issues.jboss.org/browse/DROOLS-3741.
> The styles used in the current implementation might present usability concerns - the Decision/Scenario list type size is very small and could pose a readability issue. The layout and alignment of the test summary data is difficult to scan, due to the gutter alignment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years