[JBoss JIRA] (SWSQE-178) Abstract Details Page - Parser
by Hayk Hovsepyan (JIRA)
Hayk Hovsepyan created SWSQE-178:
------------------------------------
Summary: Abstract Details Page - Parser
Key: SWSQE-178
URL: https://issues.jboss.org/browse/SWSQE-178
Project: Kiali QE
Issue Type: Task
Reporter: Hayk Hovsepyan
Assignee: Michael Foley
For each Details page we have in Kiali UI, we need a separate Object to get the fields and use them in tests assertions.
But it requires special Abstract class for generally Details page for React, which will parse and read all values into a Matrix, so each extended class will use that matrix cells for returning field related getter method.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-178) Abstract Details Page - Parser
by Hayk Hovsepyan (JIRA)
[ https://issues.jboss.org/browse/SWSQE-178?page=com.atlassian.jira.plugin.... ]
Hayk Hovsepyan updated SWSQE-178:
---------------------------------
Team: Automation
Sprint: Kiali QE Sprint 4
> Abstract Details Page - Parser
> ------------------------------
>
> Key: SWSQE-178
> URL: https://issues.jboss.org/browse/SWSQE-178
> Project: Kiali QE
> Issue Type: Task
> Reporter: Hayk Hovsepyan
> Assignee: Michael Foley
>
> For each Details page we have in Kiali UI, we need a separate Object to get the fields and use them in tests assertions.
> But it requires special Abstract class for generally Details page for React, which will parse and read all values into a Matrix, so each extended class will use that matrix cells for returning field related getter method.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2487) Make Parallel Rules Build Threshold configurable.
by Duncan Doyle (JIRA)
Duncan Doyle created DROOLS-2487:
------------------------------------
Summary: Make Parallel Rules Build Threshold configurable.
Key: DROOLS-2487
URL: https://issues.jboss.org/browse/DROOLS-2487
Project: Drools
Issue Type: Enhancement
Components: core engine
Affects Versions: 7.7.0.Final
Reporter: Duncan Doyle
Assignee: Mario Fusco
Currently, the threshold for parallel rules build is fixed and set to 10. It would be nice if we can configure this threshold, and even be able to fully disable parallel builds (for example by setting the value to -1) in case of problems with the parallel builds.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10029) bean-discovery-mode="annotated" is not working like described in the spec
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-10029?page=com.atlassian.jira.plugin... ]
Martin Kouba resolved WFLY-10029.
---------------------------------
Resolution: Cannot Reproduce
Feel free to reopen and provide a reproducer, i.e. a minimal "failing" app so that we could investigate the problem.
> bean-discovery-mode="annotated" is not working like described in the spec
> -------------------------------------------------------------------------
>
> Key: WFLY-10029
> URL: https://issues.jboss.org/browse/WFLY-10029
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 10.1.0.Final
> Reporter: Ralph Soika
> Assignee: Martin Kouba
> Priority: Minor
> Labels: beans.xml
>
> I think we have a problem in Wildfly 10 concerning scanning of CDI Beans. Take a look at the following example:
> {code:java}
> @Stateless
> @LocalBean
> public class SomeService {
> ...
> }
> public class SomeClass {
> @EJB
> SomeService someService;
> ....
> }
> {code}
> We have a stateless session ejb an a bean which is not annotated with a scope but is injecting the service EJB. If you use a beans.xml with the tag:
> {noformat}
> bean-discovery-mode="annotated"
> {noformat}
> this works in wildfly 10 - the _someService_ is injected into the _someClass_ which is treated as a CDI bean. But this is not a correct behavior as stated in the specification. It says, that in this case only beans with a scope annotation should be treated as CDI which is not the case for SomeClass. Normally, as a developer, you would not complain much about this. So this is only a minor issue.
> I recognized this after I tried to run my application on Glassfish/Payara4 which did no longer work until I changed the beans.xml tag to:
> {noformat}
> bean-discovery-mode="all"
> {noformat}
> Now it works in both application servers. I think in wildfly we are misinterpreting the attribute "bean-discovery-mode". I think this should be changed in the next versions for EE8. I don't know if this behavior is a known issue and maybe it is still under development.
> I know also that with such a change some projects (also my own ones) will break. So maybe a new configuration switch like "strict-cdi-scanning" is helpful. What do you think?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years