January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11628) [EAT] : jackson-databind: improper polymorphic deserialization in openjpa class testcase for all the servers

by Panagiotis Sotiropoulos (Jira)

[ https://issues.jboss.org/browse/WFLY-11628?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos moved JBEAP-16275 to WFLY-11628: -------------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11628 (was: JBEAP-16275) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Testing/Validation) > [EAT] : jackson-databind: improper polymorphic deserialization in openjpa class testcase for all the servers > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11628 > URL: https://issues.jboss.org/browse/WFLY-11628 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Improper polymorphic deserialization in openjpa class testcase for all the servers -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11628) [EAT] : jackson-databind: improper polymorphic deserialization in openjpa class testcase for all the servers

by Panagiotis Sotiropoulos (Jira)

[ https://issues.jboss.org/browse/WFLY-11628?page=com.atlassian.jira.plugin... ] Panagiotis Sotiropoulos resolved WFLY-11628. -------------------------------------------- Resolution: Done > [EAT] : jackson-databind: improper polymorphic deserialization in openjpa class testcase for all the servers > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-11628 > URL: https://issues.jboss.org/browse/WFLY-11628 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Improper polymorphic deserialization in openjpa class testcase for all the servers -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11627?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-11627: ------------------------------------------- [~dmlloyd], [~brian.stansberry] - any input on this? > ExampleDS is requirement for applications that don't mandate it. > ---------------------------------------------------------------- > > Key: WFLY-11627 > URL: https://issues.jboss.org/browse/WFLY-11627 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11627?page=com.atlassian.jira.plugin... ] Bartosz Baranowski reassigned WFLY-11627: ----------------------------------------- Assignee: Bartosz Baranowski (was: Brian Stansberry) > ExampleDS is requirement for applications that don't mandate it. > ---------------------------------------------------------------- > > Key: WFLY-11627 > URL: https://issues.jboss.org/browse/WFLY-11627 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11627?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-11627: ------------------------------------------- jboss-logging quickstart is simple JSP: {noformat} <body> <% LoggingExample.logDebug(); LoggingExample.logError(); LoggingExample.logFatal(); LoggingExample.logInfo(); LoggingExample.logTrace(); LoggingExample.logWarn(); %> Log Messages have been written. Please check your console as well as <i>EAP_HOME</i>/standalone/log for messages. </body> {noformat} {code:title=LoggingExample.java|borderStyle=solid} public class LoggingExample { // a JBoss Logging 3 style level (FATAL, ERROR, WARN, INFO, DEBUG, TRACE), or a special level (OFF, ALL). private static Logger log = Logger.getLogger(LoggingExample.class.getName()); static { logFatal(); logError(); logWarn(); logInfo(); logDebug(); logTrace(); } public static void logFatal() { if (log.isEnabled(Logger.Level.FATAL)) { log.fatal("THIS IS A FATAL MESSAGE"); } } public static void logError() { if (log.isEnabled(Logger.Level.ERROR)) { log.error("THIS IS AN ERROR MESSAGE"); } } public static void logWarn() { if (log.isEnabled(Logger.Level.WARN)) { log.warn("THIS IS A WARNING MESSAGE"); } } public static void logInfo() { if (log.isEnabled(Logger.Level.INFO)) { log.info("THIS IS AN INFO MESSAGE"); } } public static void logDebug() { if (log.isEnabled(Logger.Level.DEBUG)) { log.debug("THIS IS A DEBUG MESSAGE"); } } public static void logTrace() { if (log.isEnabled(Logger.Level.TRACE)) { log.trace("THIS IS A TRACE MESSAGE"); } } } {code} > ExampleDS is requirement for applications that don't mandate it. > ---------------------------------------------------------------- > > Key: WFLY-11627 > URL: https://issues.jboss.org/browse/WFLY-11627 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11604) Non-anonymous principal is not propagated from EJB context to CDI bean

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFLY-11604?page=com.atlassian.jira.plugin... ] Martin Choma commented on WFLY-11604: ------------------------------------- PicketBox, Nikoleta was basically following documentation https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap... . Fact that ctx.getCallerPrincipal() returns correct principal makes us think configuration is correct. But we are not sure if this assumption is correct. > Non-anonymous principal is not propagated from EJB context to CDI bean > ---------------------------------------------------------------------- > > Key: WFLY-11604 > URL: https://issues.jboss.org/browse/WFLY-11604 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 14.0.1.Final, 15.0.1.Final > Reporter: Nikoleta Žiaková > Assignee: Matej Novotny > Priority: Critical > > This is a follow-up on WFLY-11587 which only dealt with being able to inject the principal. > However, during testing I have tried a scenario when the caller principal was not anonymous (run-as-principal setting in jboss-ejb3.xml). See the test case in this [commit|https://github.com/nziakova/wildfly/commit/9ae586ad0159e6399f65103...]. > The principal is not propagated from the EJB context. The result is that injected principal in the CDI bean is always anonymous, although {{ctx.getCallerPrincipal()}} in the EJB returns correct principal. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3492: --------------------------------------- [~zhutaojiajia] I like the proposal, just some comments: - I think we can remove "Test Tools" that now is just a static title and keep directly "Test Editor", "Scenario Cheatsheet" etc - I would prefer something in the middle between Design 1 and Design 2: read only by default but edit inline when you click on edit without a popup - "Skip from the build" should be a like all the other settings and not in a specific section (as checkbox probably) [~kkufova] I agree with you proposal but I prefer to move Test Report just above Test Coverage icon instead of the opposite. > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png, 屏幕快照 2019-01-22 下午4.44.04.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11627?page=com.atlassian.jira.plugin... ] Bartosz Baranowski updated WFLY-11627: -------------------------------------- Steps to Reproduce: * /subsystem=datasources/data-source=ExampleDS:write-attribute(name=enabled,value=false) * :reload * deploy ~/redhat/git/quickstart/logging/target/jboss-logging.war > ExampleDS is requirement for applications that don't mandate it. > ---------------------------------------------------------------- > > Key: WFLY-11627 > URL: https://issues.jboss.org/browse/WFLY-11627 > Project: WildFly > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11627) ExampleDS is requirement for applications that don't mandate it.

by Bartosz Baranowski (Jira)

Bartosz Baranowski created WFLY-11627: ----------------------------------------- Summary: ExampleDS is requirement for applications that don't mandate it. Key: WFLY-11627 URL: https://issues.jboss.org/browse/WFLY-11627 Project: WildFly Issue Type: Bug Reporter: Bartosz Baranowski Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3492) Create UX proposal to show/edit Test Scenario (Preview) global setting

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3492?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3492: -------------------------------------- [~zhutaojiajia], this looks great, thanks! Maybe we can even move the Coverage report below the Test report, as these items are closely connected. What do you think? > Create UX proposal to show/edit Test Scenario (Preview) global setting > ---------------------------------------------------------------------- > > Key: DROOLS-3492 > URL: https://issues.jboss.org/browse/DROOLS-3492 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: tao zhu > Priority: Major > Labels: ScenarioSimulation, UXD, UXTeam > Attachments: 11unnamed.png, TestScenario_Cheatsheet.png, TestScenario_TestEditor.png, TestScenario_TestReport.png, TestScenario_whole.png, test-report-icon.png, 屏幕快照 2019-01-22 下午4.44.04.png > > > As user I want to be able to see/edit editor global settings. > For instance DMN file linked to the scenario or the Session name of a Rule scenario -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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 January 2019