[JBoss JIRA] (DROOLS-5070) "Discard unsaved changes and proceed" pop up is displayed even if we close the editor after clicking on "Save" button for guided rule editor.
by Sudhish Nair (Jira)
[ https://issues.redhat.com/browse/DROOLS-5070?page=com.atlassian.jira.plug... ]
Sudhish Nair moved RHDM-1245 to DROOLS-5070:
--------------------------------------------
Project: Drools (was: Red Hat Decision Manager)
Key: DROOLS-5070 (was: RHDM-1245)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Decision Table Editor
(was: Decision Central)
Affects Version/s: 7.32.0.Final
(was: 7.6.0.GA)
QE Status: NEW
> "Discard unsaved changes and proceed" pop up is displayed even if we close the editor after clicking on "Save" button for guided rule editor.
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-5070
> URL: https://issues.redhat.com/browse/DROOLS-5070
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.32.0.Final
> Reporter: Sudhish Nair
> Assignee: Michael Anstis
> Priority: Major
> Labels: support
>
> "Discard unsaved changes and proceed" pop up is displayed even if we close the editor after clicking on "Save" button for guided rule editor.
> Changes seem to be getting saved on the click of "Save" button in the back end but still if click on close icon popup is displayed. Editor gets closed successfully if we click the save button again.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5046) [DMN Designer] Marshalling questions
by Edson Tirelli (Jira)
[ https://issues.redhat.com/browse/DROOLS-5046?page=com.atlassian.jira.plug... ]
Edson Tirelli commented on DROOLS-5046:
---------------------------------------
[~manstis] IMO, setting the "id" attribute for the elements is not a problem, and eventually might help with debugging as it is usually used as key to reference to elements within a DMN model. So, I would still set them.
All other optional attributes you listed above should not be set, unless explicitly set by the user in the model itself.
Also, good catch on Rule Annotation.
> [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, 2 months
[JBoss JIRA] (DROOLS-3003) Enhance performance of PMML using decision trees
by Edson Tirelli (Jira)
[ https://issues.redhat.com/browse/DROOLS-3003?page=com.atlassian.jira.plug... ]
Edson Tirelli reassigned DROOLS-3003:
-------------------------------------
Assignee: Gabriele Cardosi (was: Edson Tirelli)
> Enhance performance of PMML using decision trees
> ------------------------------------------------
>
> Key: DROOLS-3003
> URL: https://issues.redhat.com/browse/DROOLS-3003
> Project: Drools
> Issue Type: Enhancement
> Components: PMML
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: PMMLRefactor
>
> Refactor the generation of rules and classes by the PMMLCompiler, for PMML resources containing Tree models.
> # Replace any remaining instances of types declared in rules files with POJOs
> # Reduce and/or remove the usage of rules in the process of generating rules and classes
> # Expose/make available the POJO that is generated from the MiningSchema, so that it can be used as input, instead of PMMLRequestData type
> # Update rules to make direct use of the input POJO
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBEE-251) FactoryFinderCache failed to read implementation when comments present
by Alexey Markevich (Jira)
[ https://issues.redhat.com/browse/JBEE-251?page=com.atlassian.jira.plugin.... ]
Alexey Markevich commented on JBEE-251:
---------------------------------------
According to ServiceLoader javadoc
{quote}The comment character is '#'{quote}
1. https://docs.oracle.com/javase/8/docs/api/java/util/ServiceLoader.html
> FactoryFinderCache failed to read implementation when comments present
> ----------------------------------------------------------------------
>
> Key: JBEE-251
> URL: https://issues.redhat.com/browse/JBEE-251
> Project: JBoss Enterprise Spec APIs
> Issue Type: Bug
> Components: jboss-el-api
> Reporter: Alexey Markevich
> Assignee: Scott Marlow
> Priority: Major
>
> Since Tomcat 9.0.31 [1] introduced ServiceLoader entry to META-INF for EL [2] following exception occurred [3].
> The same for 'jakarta.el:jakarta.el-api:3.0.3' and its FactoryFinder.
> 1. https://tomcat.apache.org/tomcat-9.0-doc/changelog.html
> 2. https://github.com/apache/tomcat/blob/9.0.31/res/META-INF/jasper-el.jar/s...
> 3.
> Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]
> at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
> at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
> ... 40 more
> Caused by: javax.el.ELException: Provider # Licensed to the Apache Software Foundation (ASF) under one or more not found
> at javax.el.FactoryFinder.newInstance(FactoryFinder.java:64)
> at javax.el.FactoryFinder.find(FactoryFinder.java:103)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:140)
> at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:110)
> at org.apache.jasper.runtime.JspApplicationContextImpl.<init>(JspApplicationContextImpl.java:49)
> at org.apache.jasper.runtime.JspApplicationContextImpl.getInstance(JspApplicationContextImpl.java:78)
> at org.apache.jasper.runtime.JspFactoryImpl.getJspApplicationContext(JspFactoryImpl.java:217)
> at org.jboss.weld.environment.servlet.WeldServletLifecycle.initialize(WeldServletLifecycle.java:219)
> at org.jboss.weld.environment.servlet.EnhancedListener.onStartup(EnhancedListener.java:62)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5135)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
> ... 46 more
> Caused by: java.lang.ClassNotFoundException: # Licensed to the Apache Software Foundation (ASF) under one or more
> at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1365)
> at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
> at javax.el.FactoryFinder.newInstance(FactoryFinder.java:48)
> ... 56 more
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JBEE-251) FactoryFinderCache failed to read implementation when comments present
by Alexey Markevich (Jira)
Alexey Markevich created JBEE-251:
-------------------------------------
Summary: FactoryFinderCache failed to read implementation when comments present
Key: JBEE-251
URL: https://issues.redhat.com/browse/JBEE-251
Project: JBoss Enterprise Spec APIs
Issue Type: Bug
Components: jboss-el-api
Reporter: Alexey Markevich
Assignee: Scott Marlow
Since Tomcat 9.0.31 [1] introduced ServiceLoader entry to META-INF for EL [2] following exception occurred [3].
The same for 'jakarta.el:jakarta.el-api:3.0.3' and its FactoryFinder.
1. https://tomcat.apache.org/tomcat-9.0-doc/changelog.html
2. https://github.com/apache/tomcat/blob/9.0.31/res/META-INF/jasper-el.jar/s...
3.
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]
at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:134)
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909)
... 40 more
Caused by: javax.el.ELException: Provider # Licensed to the Apache Software Foundation (ASF) under one or more not found
at javax.el.FactoryFinder.newInstance(FactoryFinder.java:64)
at javax.el.FactoryFinder.find(FactoryFinder.java:103)
at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:140)
at javax.el.ExpressionFactory.newInstance(ExpressionFactory.java:110)
at org.apache.jasper.runtime.JspApplicationContextImpl.<init>(JspApplicationContextImpl.java:49)
at org.apache.jasper.runtime.JspApplicationContextImpl.getInstance(JspApplicationContextImpl.java:78)
at org.apache.jasper.runtime.JspFactoryImpl.getJspApplicationContext(JspFactoryImpl.java:217)
at org.jboss.weld.environment.servlet.WeldServletLifecycle.initialize(WeldServletLifecycle.java:219)
at org.jboss.weld.environment.servlet.EnhancedListener.onStartup(EnhancedListener.java:62)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5135)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
... 46 more
Caused by: java.lang.ClassNotFoundException: # Licensed to the Apache Software Foundation (ASF) under one or more
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1365)
at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
at javax.el.FactoryFinder.newInstance(FactoryFinder.java:48)
... 56 more
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months