[JBoss JIRA] (WFLY-10655) SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"
by Farah Juma (Jira)
[ https://issues.redhat.com/browse/WFLY-10655?page=com.atlassian.jira.plugi... ]
Farah Juma reassigned WFLY-10655:
---------------------------------
Assignee: (was: Dmitrii Tikhomirov)
> SEVERE error on deploy of ear: "Unable to obtain CDI 1.1 utilities for Mojarra"
> -------------------------------------------------------------------------------
>
> Key: WFLY-10655
> URL: https://issues.redhat.com/browse/WFLY-10655
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 13.0.0.Final
> Reporter: Tommasso Borgato
> Priority: Major
> Labels: downstream_dependency
> Fix For: 14.0.0.Beta2
>
> Attachments: clusterbench-ee7-bugged.ear, clusterbench-ee7.ear
>
>
> Affected scenario is [eap-7x-failover-ejb-ejbservlet-undeploy-repl-sync|https://jenkins.hosts.m...].
> Every time the server is stated or re-started, we observed the following SEVERE logs just after clusterbench is deployed (clusterbench is an ear that uses JSF); we observed them systematically on each of the 4 nodes composing the cluster:
> {noformat}
> 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 72) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-granular.war cache from web container
> 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started client-mappings cache from ejb container
> 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 73) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-default.war cache from web container
> 2018-06-27 02:47:07,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started default-server cache from web container
> 2018-06-27 02:47:07,439 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started clusterbench-ee7.ear.clusterbench-ee7-web-passivating.war cache from web container
> 2018-06-27 02:47:07,578 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 75) WFLYCLINF0002: Started clusterbench-ee7.ear/clusterbench-ee7-ejb.jar cache from ejb container
> 2018-06-27 02:47:07,673 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.jberet.creation.BatchBeanProducer is deprecated from CDI 1.1!
> 2018-06-27 02:47:07,713 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor is deprecated from CDI 1.1!
> 2018-06-27 02:47:07,739 WARN [org.jboss.weld.Bootstrap] (MSC service thread 1-7) WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
> 2018-06-27 02:47:08,149 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
> 2018-06-27 02:47:08,163 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
> 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 76) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-granular'
> 2018-06-27 02:47:08,586 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 72) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench'
> 2018-06-27 02:47:08,587 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 78) Initializing Mojarra 2.2.13.SP5 for context '/clusterbench-passivating'
> 2018-06-27 02:47:09,860 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 76) WFLYUT0021: Registered web context: '/clusterbench-granular' for server 'default-server'
> 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0021: Registered web context: '/clusterbench' for server 'default-server'
> 2018-06-27 02:47:09,863 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/clusterbench-passivating' for server 'default-server'
> 2018-06-27 02:47:09,889 INFO [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 2018-06-27 02:47:09,989 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
> {noformat}
>
> Complete log [here|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/job/perflab_eap...]
> Already observed a very long time ago: https://issues.jboss.org/browse/WFLY-1946
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5046?page=com.atlassian.jira.plug... ]
Michael Anstis commented on DROOLS-5046:
----------------------------------------
[~tirelli] [~tari_manga] Please see this JIRA description.
I found some differences when comparing the results of marshalling "Payment Date" with our marshaller vs _other tools_.
Can you please advise whether we need to fix any of them (other than support for RuleAnnotation)?
> [DMN Designer] Marshalling questions
> ------------------------------------
>
> Key: DROOLS-5046
> URL: https://issues.redhat.com/browse/DROOLS-5046
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.33.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> Our marshaller is EXPLICITLY setting Definitions.typeLanguage to FEEL. Is this acceptable?
> DMN1.2 Specification "6.3.2 Definitions metamodel" states :
> An instance of Definitions MAY specify a typeLanguage, which is a URI that identifies the default type language used in elements within the scope of this Definitions ... If unspecified, the default typeLanguage is FEEL.
> So it is not wrong, but it is not necessary.
> ---------------------------------------------------------------------------------
> Our marshaller is EXPLICITLY setting ItemDefinition.id
> DMN1.2 Specification "7.3.2 - ItemDefinition metamodel" states :
> ...an instance of ItemDefinition HAS a name and an OPTIONAL id
> So it is not wrong, but it is not necessary.
> ---------------------------------------------------------------------------------
> Our marshaller IS NOT setting ContextEntry.id
> DMN1.2 Specification 10.5.2 - ContextEntry metamodel states :
> ...ContextEntry is a specialization of DMNElement, from which it INHERITS the OPTIONAL id...
> It is therefore correct for us to exclude the id (but _other tools_ includes it. Is that wrong?!)
> ---------------------------------------------------------------------------------
> Our marshaller is EXPLICITLY setting DecisionTable.preferredOrientation (to Rule-as-Row)
> DMN1.2 Specification 8.3.1 - Decision Table metamodel states :
> ...It has a preferredOrientation, which SHALL be one of the enumerated DecisionTableOrientation.
> It is therefore not wrong for us to include preferredOrientation and seems mandatory.
> ---------------------------------------------------------------------------------
> Our marshaller is EXPLICITLY setting inputExpression.id.
> DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel:-
> ...An instance of InputClause is made of an optional inputExpression... [where an inputExpression is an Expression].
> There is not mention as to whether the Expression inherits its id or needs one explicitly defined.
> Is it therefore incorrect for us to include the id?
> ---------------------------------------------------------------------------------
> Our marshaller IS NOT setting outputEntry.expressionLanguage.
> DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel states (well does NOT state anything!) :
> OutputClause does not appear to have an expressionLanguage property; only the UnaryTests that is encapsulated by OutputClause supports it.
> Is this an issue with _other tools_'s marshaller?
> ---------------------------------------------------------------------------------
> [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation
> https://issues.redhat.com/browse/DROOLS-5045
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions
by Michael Anstis (Jira)
[ https://issues.redhat.com/browse/DROOLS-5046?page=com.atlassian.jira.plug... ]
Michael Anstis updated DROOLS-5046:
-----------------------------------
Tester: Jozef Marko
Labels: drools-tools (was: )
> [DMN Designer] Marshalling questions
> ------------------------------------
>
> Key: DROOLS-5046
> URL: https://issues.redhat.com/browse/DROOLS-5046
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.33.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Major
> Labels: drools-tools
>
> Our marshaller is EXPLICITLY setting Definitions.typeLanguage to FEEL. Is this acceptable?
> DMN1.2 Specification "6.3.2 Definitions metamodel" states :
> An instance of Definitions MAY specify a typeLanguage, which is a URI that identifies the default type language used in elements within the scope of this Definitions ... If unspecified, the default typeLanguage is FEEL.
> So it is not wrong, but it is not necessary.
> ---------------------------------------------------------------------------------
> Our marshaller is EXPLICITLY setting ItemDefinition.id
> DMN1.2 Specification "7.3.2 - ItemDefinition metamodel" states :
> ...an instance of ItemDefinition HAS a name and an OPTIONAL id
> So it is not wrong, but it is not necessary.
> ---------------------------------------------------------------------------------
> Our marshaller IS NOT setting ContextEntry.id
> DMN1.2 Specification 10.5.2 - ContextEntry metamodel states :
> ...ContextEntry is a specialization of DMNElement, from which it INHERITS the OPTIONAL id...
> It is therefore correct for us to exclude the id (but _other tools_ includes it. Is that wrong?!)
> ---------------------------------------------------------------------------------
> Our marshaller is EXPLICITLY setting DecisionTable.preferredOrientation (to Rule-as-Row)
> DMN1.2 Specification 8.3.1 - Decision Table metamodel states :
> ...It has a preferredOrientation, which SHALL be one of the enumerated DecisionTableOrientation.
> It is therefore not wrong for us to include preferredOrientation and seems mandatory.
> ---------------------------------------------------------------------------------
> Our marshaller is EXPLICITLY setting inputExpression.id.
> DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel:-
> ...An instance of InputClause is made of an optional inputExpression... [where an inputExpression is an Expression].
> There is not mention as to whether the Expression inherits its id or needs one explicitly defined.
> Is it therefore incorrect for us to include the id?
> ---------------------------------------------------------------------------------
> Our marshaller IS NOT setting outputEntry.expressionLanguage.
> DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel states (well does NOT state anything!) :
> OutputClause does not appear to have an expressionLanguage property; only the UnaryTests that is encapsulated by OutputClause supports it.
> Is this an issue with _other tools_'s marshaller?
> ---------------------------------------------------------------------------------
> [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation
> https://issues.redhat.com/browse/DROOLS-5045
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions
by Michael Anstis (Jira)
Michael Anstis created DROOLS-5046:
--------------------------------------
Summary: [DMN Designer] Marshalling questions
Key: DROOLS-5046
URL: https://issues.redhat.com/browse/DROOLS-5046
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.33.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
Our marshaller is EXPLICITLY setting Definitions.typeLanguage to FEEL. Is this acceptable?
DMN1.2 Specification "6.3.2 Definitions metamodel" states :
An instance of Definitions MAY specify a typeLanguage, which is a URI that identifies the default type language used in elements within the scope of this Definitions ... If unspecified, the default typeLanguage is FEEL.
So it is not wrong, but it is not necessary.
---------------------------------------------------------------------------------
Our marshaller is EXPLICITLY setting ItemDefinition.id
DMN1.2 Specification "7.3.2 - ItemDefinition metamodel" states :
...an instance of ItemDefinition HAS a name and an OPTIONAL id
So it is not wrong, but it is not necessary.
---------------------------------------------------------------------------------
Our marshaller IS NOT setting ContextEntry.id
DMN1.2 Specification 10.5.2 - ContextEntry metamodel states :
...ContextEntry is a specialization of DMNElement, from which it INHERITS the OPTIONAL id...
It is therefore correct for us to exclude the id (but _other tools_ includes it. Is that wrong?!)
---------------------------------------------------------------------------------
Our marshaller is EXPLICITLY setting DecisionTable.preferredOrientation (to Rule-as-Row)
DMN1.2 Specification 8.3.1 - Decision Table metamodel states :
...It has a preferredOrientation, which SHALL be one of the enumerated DecisionTableOrientation.
It is therefore not wrong for us to include preferredOrientation and seems mandatory.
---------------------------------------------------------------------------------
Our marshaller is EXPLICITLY setting inputExpression.id.
DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel:-
...An instance of InputClause is made of an optional inputExpression... [where an inputExpression is an Expression].
There is not mention as to whether the Expression inherits its id or needs one explicitly defined.
Is it therefore incorrect for us to include the id?
---------------------------------------------------------------------------------
Our marshaller IS NOT setting outputEntry.expressionLanguage.
DMN1.2 Specification 8.3.2 - Decision Table Input and Output metamodel states (well does NOT state anything!) :
OutputClause does not appear to have an expressionLanguage property; only the UnaryTests that is encapsulated by OutputClause supports it.
Is this an issue with _other tools_'s marshaller?
---------------------------------------------------------------------------------
[DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation
https://issues.redhat.com/browse/DROOLS-5045
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5045) [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation
by Michael Anstis (Jira)
Michael Anstis created DROOLS-5045:
--------------------------------------
Summary: [DMN Designer] Marshaller does not support DMN1.2 DecisionTable RuleAnnotation
Key: DROOLS-5045
URL: https://issues.redhat.com/browse/DROOLS-5045
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.33.0.Final
Reporter: Michael Anstis
Assignee: Michael Anstis
DMN1.2 has RuleAnnotation in the DecisionTable expression.
Our marshallers (-backend and -client) do not support it and use the Expression's Description element for the DecisionRule description column. We also need to enhance the UI to support adding/deleting additional RuleAnnotations.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml
by Michael Biarnes Kiefer (Jira)
[ https://issues.redhat.com/browse/DROOLS-2254?page=com.atlassian.jira.plug... ]
Michael Biarnes Kiefer updated DROOLS-2254:
-------------------------------------------
Fix Version/s: 7.34.0.Final
(was: 7.33.0.Final)
> Automate .proto files rebuild in pom.xml
> ----------------------------------------
>
> Key: DROOLS-2254
> URL: https://issues.redhat.com/browse/DROOLS-2254
> Project: Drools
> Issue Type: Task
> Components: tools
> Affects Versions: 7.5.0.Final
> Reporter: Dmitry Volodin
> Assignee: Dmitry Volodin
> Priority: Minor
> Fix For: 7.34.0.Final
>
>
> According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files.
> This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months
[JBoss JIRA] (DROOLS-5034) Test scenario grid does not adjust correctly
by Daniele Zonca (Jira)
[ https://issues.redhat.com/browse/DROOLS-5034?page=com.atlassian.jira.plug... ]
Daniele Zonca reassigned DROOLS-5034:
-------------------------------------
Assignee: Yeser Amer (was: Daniele Zonca)
> Test scenario grid does not adjust correctly
> --------------------------------------------
>
> Key: DROOLS-5034
> URL: https://issues.redhat.com/browse/DROOLS-5034
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.33.0.Final
> Reporter: Anna Dupliak
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Screencast from 02-11-2020.webm, bpms_Traffic-1.zip
>
>
> When user opens grid and scrolls to the edge of table horizontally and hides the Tools Panel then grid is not fitting to the size of the editor. See the [^Screencast from 02-11-2020.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 3 months