[JBoss JIRA] (DROOLS-3474) Create HTML and CSS for List/Map data objects
by tao zhu (Jira)
[ https://issues.jboss.org/browse/DROOLS-3474?page=com.atlassian.jira.plugi... ]
tao zhu commented on DROOLS-3474:
---------------------------------
[~aglass] #7 icon to remain visible is make sense to me.Thank you.
[~srambach] Thanks for your updates. There are 3 very small problems.
!Rectangle.png|thumbnail!
1. A small problem of modal padding.There are space between the line and grey background.
2. The dangling vertical line is a little strange. There is a horizontal line on the top of modal footer. Could you help me add a horizontal line?
3. The button of “+ Add phones” should left align with the title of “Phones”
> Create HTML and CSS for List/Map data objects
> ---------------------------------------------
>
> Key: DROOLS-3474
> URL: https://issues.jboss.org/browse/DROOLS-3474
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Amy Glass
> Assignee: Sarah Rambacher
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Rectangle.png, Rectangle.png, firefox.png
>
>
> Provide HTML and CSS for the designs in Drools-3098.
> Will first provide HTML structure, and follow up with CSS styling.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (WFCORE-4267) dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers
by jaikiran pai (Jira)
jaikiran pai created WFCORE-4267:
------------------------------------
Summary: dump-all-threads management operation forces explicit setting of locked-monitors and locked-syncrhonizers
Key: WFCORE-4267
URL: https://issues.jboss.org/browse/WFCORE-4267
Project: WildFly Core
Issue Type: Bug
Components: Management
Affects Versions: 7.0.0.Final
Environment: WildFly server 15.0.0.Final
Reporter: jaikiran pai
Assignee: Jeff Mesnil
The {{dump-all-threads}} exposed by {{/core-service=platform-mbean/type=threading}} has this resource operation description:
{code}
....
"request-properties" => {
"locked-monitors" => {
"type" => BOOLEAN,
"description" => "A list of detyped representations java.lang.management.MonitorInfo objects, each of w
hich represents an object monitor currently locked by the thread.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
},
"locked-synchronizers" => {
"type" => BOOLEAN,
"description" => "A list of detyped representations java.lang.management.LockInfo objects, each of whic
h represents an ownable synchronizer currently locked by the thread.",
"expressions-allowed" => false,
"required" => false,
"nillable" => true,
"default" => false
}
...
{code}
The {{locked-monitors}} and {{locked-synchronizers}} both are mentioned as {{required=false}} and with default values. However, when I run this operation as follows on a (standalone) WildFly 15.0.0.Final instance:
{code}
/core-service=platform-mbean/type=threading:dump-all-threads
{code}
I get:
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: 'locked-synchronizers' may not be null",
"rolled-back" => true
}
{code}
when I then pass, locked-synchronizers explicitly as an attribute, it then complains about locked-monitors being absent. The only way to get past this is to specify both those attributes in the operation.
By the way, the description of those attributes isn't too clear, IMO. Is it saying that the attribute represents a "list of detyped representations ...." ? In which case the type of BOOLEAN for that attribute would be incorrect. Or does it mean that if set to true then a "list of detyped representations ...." will be returned?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3429) Serialization of KiePackages fails when SecurityManager is enabled
by Marcel Abou Khalil (Jira)
[ https://issues.jboss.org/browse/DROOLS-3429?page=com.atlassian.jira.plugi... ]
Marcel Abou Khalil commented on DROOLS-3429:
--------------------------------------------
Hi [~tzimanyi], all looks good to me, thanks for the effort :-)
I'm not familiar with the release cycle for drools. When will a new release including this fix be available?
> Serialization of KiePackages fails when SecurityManager is enabled
> ------------------------------------------------------------------
>
> Key: DROOLS-3429
> URL: https://issues.jboss.org/browse/DROOLS-3429
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final, 7.15.0.Final
> Environment: Running with IBM JDK 1.8
> Reporter: Marcel Abou Khalil
> Assignee: Tibor Zimányi
> Priority: Major
>
> Our Drools setup:
> - users write rules in a combination of DSL and Java code
> - rules are compiled
> - packages are stored in a database (rules are seldom changed but often ran)
> This has been working fine but in order to improve security, we've enabled the SecurityManager. This throws an exception while trying to serialize the consequence part of the rule:
> {code:java}
> Caused by: java.io.NotSerializableException: com.redacted.Rule_Events_REDACTED61028857611DefaultConsequenceInvoker
> - field (class "org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence", name: "delegate", type: "interface org.drools.core.spi.Consequence")
> - object (class "org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence", org.drools.core.definitions.rule.impl.RuleImpl$SafeConsequence@93071816)
> - writeExternal data
> - object (class "org.drools.core.definitions.rule.impl.RuleImpl", [Rule name=REDACTED, agendaGroup=end, salience=0, no-loop=true])
> - writeExternal data
> - object (class "org.drools.core.rule.JavaDialectRuntimeData", org.drools.core.rule.JavaDialectRuntimeData{...})
> - custom writeObject data (class "java.util.HashMap")
> - object (class "java.util.HashMap", {java=org.drools.core.rule.JavaDialectRuntimeData{...}, mvel=org.drools.core.rule.MVELDialectRuntimeData@b99ea6b2})
> - writeExternal data
> - root object (class "org.drools.core.rule.DialectRuntimeRegistry", org.drools.core.rule.DialectRuntimeRegistry@2d9acae8)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1213)
> at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1615)
> at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1576)
> at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1499)
> at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1209)
> at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:365)
> at org.drools.core.definitions.rule.impl.RuleImpl.writeExternal(RuleImpl.java:180)
> {code}
> Possible cause:
> Class {{RuleImpl}}, method {{writeExternal}} will write out {{null}} if the consequence is of type {{CompiledInvoker}}. But if the SecurityManager is enabled, the method {{wire}} will wrap the Consequence inside a {{SafeConsequence}}. A {{SafeConsequence}}, in contrast to the wrapped consequence is not a {{CompiledInvoker}}, so {{writeExternal}} will attempt to serialize it, instead of just writing {{null}} and fails.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (DROOLS-3481) Data type constraints: DMN canvas view workflow
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3481?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3481:
-------------------------------------
[~tirelli] [~karreiro] [~manstis]
I updated the mockup for this and made a click-thru: https://redhat.invisionapp.com/share/DJPVSH5NEPG#/screens/339856080_Start
Please let me know what you think, thanks.
> Data type constraints: DMN canvas view workflow
> -----------------------------------------------
>
> Key: DROOLS-3481
> URL: https://issues.jboss.org/browse/DROOLS-3481
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> Background
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view:
> As a user, I want to be able to set data type constraints for an input value in a Decision Table, so that this constraint is valid _*only*_ in the context of this specific input in this Decision Table.
> * Provide options for:
> - one-off constraints
> - apply constraints to data type.
> - possibly "yoke" constraints to data type.
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> * Maintain "Manage" link.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months