April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-664) Test case coverage for KIALI

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-664?page=com.atlassian.jira.plugin.... ] Sunil Kondkar resolved SWSQE-664. --------------------------------- Resolution: Done Done > Test case coverage for KIALI > ---------------------------- > > Key: SWSQE-664 > URL: https://issues.jboss.org/browse/SWSQE-664 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Prachi Yadav > Priority: Major > Labels: pqi > > In test coverage graph we can see that we have covered only functional test cases. We need to include other test type of test cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method

by Christian Zambrano (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Christian Zambrano commented on WFLY-11956: ------------------------------------------- > Christian Zambrano, I don't understand. My understanding is that postConstruct() would be called after all CDI injections are performed. Calling the @PostConstruct annotated method would be the last chance to perform additional initialization, so doing the verification after that would seem to be OK. What am I missing? A class can impose a contract where a series of methods calls may have to take place on an object before a given method should be called, whether all of the required calls can be done in a PostConstruct is hard to know. Can't really come up with a real-life example. Having a method be called **outside** when it is attempted to be accessed by a client is just plain unexpected. After taking a look at the Bean Validation spec it looks like methods that comply with the JavaBean naming convention are expected to be called to validate an object so having these methods be called after the @PostConstruct is called is as good as it can get and it would solve our **current** problem > Christian Zambrano, sorry, which behavior are you referring to? I was simply trying to agree that if having a validation.xml with the contents you provided would have turned off this behavior that would have been the best answer for an app-developer to control this behavior. > @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11956 > URL: https://issues.jboss.org/browse/WFLY-11956 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, REST > Affects Versions: 16.0.0.Final > Reporter: Joerg Baesner > Assignee: Ronald Sigal > Priority: Major > Attachments: logging.txt, playground.zip > > > Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_: > {code} > @Path("/validated") > public interface ValidatedJaxRsInterface { > > @GET > @Valid > @Produces(MediaType.APPLICATION_JSON) > GreetingModel getHelloGreeting(); > } > {code} > will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed. > This can be reproduced with the attached reproducer application... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-719) Polarion Uploader - Required Fields

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-719?page=com.atlassian.jira.plugin.... ] Matthew Mahoney resolved SWSQE-719. ----------------------------------- Resolution: Done > Polarion Uploader - Required Fields > ----------------------------------- > > Key: SWSQE-719 > URL: https://issues.jboss.org/browse/SWSQE-719 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure, pqi > Attachments: Screenshot_MissingData.png, Screenshot_No-AutomationScript-MissingData.png > > > The Polarion Uploader needs to include the following fields when creating test cases, so that PQI report is accurate: > - Level > - Component > - Test Type > - Sub Type > - Description > - Verifies > - Automation / Automation Script (When Type is "Automation") -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1794) FORM Authentication should detect FORM submission BEFORE attempting to restore from cache.

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1794: ------------------------------------- Summary: FORM Authentication should detect FORM submission BEFORE attempting to restore from cache. Key: ELY-1794 URL: https://issues.jboss.org/browse/ELY-1794 Project: WildFly Elytron Issue Type: Bug Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.9.0.CR4 If a login FORM submission is received this should be higher priority than any previously cached identity. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-719) Polarion Uploader - Required Fields

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-719?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-719: ------------------------------------- Now there is no missing data for kiali. > Polarion Uploader - Required Fields > ----------------------------------- > > Key: SWSQE-719 > URL: https://issues.jboss.org/browse/SWSQE-719 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure, pqi > Attachments: Screenshot_MissingData.png, Screenshot_No-AutomationScript-MissingData.png > > > The Polarion Uploader needs to include the following fields when creating test cases, so that PQI report is accurate: > - Level > - Component > - Test Type > - Sub Type > - Description > - Verifies > - Automation / Automation Script (When Type is "Automation") -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4438) No welcome page in WildFly 17

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4438?page=com.atlassian.jira.plugi... ] Yeray Borges updated WFCORE-4438: --------------------------------- Affects Version/s: 9.0.0.Beta2 > No welcome page in WildFly 17 > ----------------------------- > > Key: WFCORE-4438 > URL: https://issues.jboss.org/browse/WFCORE-4438 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 9.0.0.Beta2, 9.0.0.Beta3 > Reporter: Jan Kasik > Assignee: Yeray Borges > Priority: Critical > Attachments: Screenshot_2019-04-23 Error.png, Screenshot_2019-04-23 Welcome to WildFly Application Server.png > > > There is no welcome/error page by default in CD17 on {{http://127.0.0.1:9990}}. See screenshots comparing WildFly 17 to 16. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4438) No welcome page in WildFly 17

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4438?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-4438: ------------------------------------ Assignee: Yeray Borges (was: Jeff Mesnil) > No welcome page in WildFly 17 > ----------------------------- > > Key: WFCORE-4438 > URL: https://issues.jboss.org/browse/WFCORE-4438 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 9.0.0.Beta3 > Reporter: Jan Kasik > Assignee: Yeray Borges > Priority: Critical > Attachments: Screenshot_2019-04-23 Error.png, Screenshot_2019-04-23 Welcome to WildFly Application Server.png > > > There is no welcome/error page by default in CD17 on {{http://127.0.0.1:9990}}. See screenshots comparing WildFly 17 to 16. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11900) Wildfly 14 + JGroups + Singleton Cluster Not Working

by Bhavesh Kharwa (Jira)

[ https://issues.jboss.org/browse/WFLY-11900?page=com.atlassian.jira.plugin... ] Bhavesh Kharwa commented on WFLY-11900: --------------------------------------- It is working fine if I start first node and wait a few second before starting a second node > Wildfly 14 + JGroups + Singleton Cluster Not Working > ---------------------------------------------------- > > Key: WFLY-11900 > URL: https://issues.jboss.org/browse/WFLY-11900 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Bhavesh Kharwa > Assignee: Paul Ferraro > Priority: Major > Fix For: 14.0.0.Final > > Attachments: app1.log, app2.log > > > Singleton cluster is not working if starts both servers at same time. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12013) (7.2.z) TCCL is not set to datasource module in datasource constructor

by Bartosz Spyrko (Jira)

Bartosz Spyrko created WFLY-12013: ------------------------------------- Summary: (7.2.z) TCCL is not set to datasource module in datasource constructor Key: WFLY-12013 URL: https://issues.jboss.org/browse/WFLY-12013 Project: WildFly Issue Type: Bug Components: JCA Affects Versions: 13.0.0.Final Reporter: Bartosz Spyrko Assignee: Stefano Maestri TCCL is not set to datasource module User has a datasource that uses ORB classes and is getting a ClassNotFound. If a 3rd party JDBC driver implementation is using e. g. CORBA, the class loader is not set and thus the CORBA classes got loaded from the 'org.jboss.as.connector' modules class loader. So the root cause is the Thread Context ClassLoader (TCCL) is not set to the classloader/module of the datasource driver module. The particular datasource driver is making using of ORB.init which is a JDK class that looks on the TCCL and other places to load the class specified in ORB.init, but JCA when running has not set the TCCL thus the classes cannot be found. Having the TCCL set to the application is how JEE handles related situations to load application classes, so it would make sense that when JCA is running the datasource that it would have the TCCL set to the module of the datasource or a delegate class loader that sees both the datasource module and any other class loader that JCA might need, JBossWS does something similar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4438) No welcome page in WildFly 17

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4438?page=com.atlassian.jira.plugi... ] Yeray Borges commented on WFCORE-4438: -------------------------------------- Hi [~brian.stansberry], it is completely unrelated, the reason is https://issues.jboss.org/browse/WFCORE-4363, which disables the error page for all the console modes. Looks like a simple fix is to disable the error handler only for ConsoleMode.NO_CONSOLE. [~jmesnil] If you are not working on this issue, you can assign it to me and I would supply a fix. > No welcome page in WildFly 17 > ----------------------------- > > Key: WFCORE-4438 > URL: https://issues.jboss.org/browse/WFCORE-4438 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 9.0.0.Beta3 > Reporter: Jan Kasik > Assignee: Jeff Mesnil > Priority: Critical > Attachments: Screenshot_2019-04-23 Error.png, Screenshot_2019-04-23 Welcome to WildFly Application Server.png > > > There is no welcome/error page by default in CD17 on {{http://127.0.0.1:9990}}. See screenshots comparing WildFly 17 to 16. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019