[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method
by Eli MacDonald (Jira)
[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ]
Eli MacDonald commented on WFLY-11956:
--------------------------------------
[~christian.zambrano] As discussed, [~ron_sigal] created [RESTEASY-2227|https://issues.jboss.org/browse/RESTEASY-2227] "Validate fields/properties after calling @PostConstruct annotated method, if one exists" to address this issue and there are pull requests waiting to be merged. The fix will go into RESTEasy 3.7.0.Final, which will ship with Wildfly 17. I will follow-up with you to discuss when the fix will be available to you.
> @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)
7 years, 2 months
[JBoss JIRA] (SWSQE-732) Migrate Off Of The Blade Center
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-732?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-732:
----------------------------------
Description:
Background information causing this Jira:
https://projects.engineering.redhat.com/browse/MWQEINFRA-720
Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
was:
Background information causing this Jira:
Embrace 2019 MW QE infrastructure vision
During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
Where we are?
Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
> Migrate Off Of The Blade Center
> -------------------------------
>
> Key: SWSQE-732
> URL: https://issues.jboss.org/browse/SWSQE-732
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matthew Mahoney
> Priority: Critical
> Labels: infrastructure
>
> Background information causing this Jira:
> https://projects.engineering.redhat.com/browse/MWQEINFRA-720
> Embrace 2019 MW QE infrastructure vision
> During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
> Where we are?
> Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
> Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
> Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-732) Mograte Off Of The Blade Center
by Matthew Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-732?page=com.atlassian.jira.plugin.... ]
Matthew Mahoney updated SWSQE-732:
----------------------------------
Priority: Critical (was: Major)
> Mograte Off Of The Blade Center
> -------------------------------
>
> Key: SWSQE-732
> URL: https://issues.jboss.org/browse/SWSQE-732
> Project: Kiali QE
> Issue Type: Story
> Reporter: Matthew Mahoney
> Priority: Critical
> Labels: infrastructure
>
> Background information causing this Jira:
> _Embrace 2019 MW QE infrastructure vision
> During the QE camp, we (MW infrastructure folks) were approached by DevOps lead architect sharing their interests around evolving MW QE infrastructure in Boston for upcoming years. I would like to reiterate what was suggested to keep MW QE part of the conversation.
> Where we are?
> Boston hardware lab is going to be consolidated into 3rd party collocation center within a year or so. Nontrivial outage is expected because of that.
> Current MW QE hardware in Boston is getting underutilized as majority of workload was moved to central CI.
> Baremetal systems (exotic architectures, performance labs, messaging labs) are getting obsolete and unreliable.
> _
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months