[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ]
Daniele Zonca updated DROOLS-3953:
----------------------------------
Description:
As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
I want to see this kind of errors in the decisions and at diagram level.
was:
As user after a test run, I want see not only the cell that are not correct (red background) but also the reason.
For instance have the possibility to see the actual value that is different from the expected or the error message.
> DMN UX - overlay validation error reporting
> -------------------------------------------
>
> Key: DROOLS-3953
> URL: https://issues.jboss.org/browse/DROOLS-3953
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ux-decision button.png, ux-decision table.png
>
>
> As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
> I want to see this kind of errors in the decisions and at diagram level.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-2214) [DMN Editor] Content of the Decision/BKM node is not copied
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-2214?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2214:
-----------------------------------
Steps to Reproduce:
# Create new DMN diagram
# Add a {{Decision}} node
# Open properties of this decision
# Set this decision as a relation
# Save the DMN diagram
# Return to DRG
# Copy the {{Decision}} node by CTRL+C shortcut
# Open properties of the decision copy node
# This {{Decision}} node won't be configured as a relation
# The same can be observed for {{BusinessKnowledgeModel}}
was:
# Create new DMN diagram
# Add a decision node
# Open properties of this decision
# Set this decision as a relation
# Save the DMN diagram
# Return to DRG
# Copy the decision node by CTRL+C shortcut
# Open properties of the decision copy node
# This decision node won't be configured as a relation
> [DMN Editor] Content of the Decision/BKM node is not copied
> -----------------------------------------------------------
>
> Key: DROOLS-2214
> URL: https://issues.jboss.org/browse/DROOLS-2214
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Priority: Major
> Labels: Stunner
>
> User has possibility to copy a DRG node by a CTRL+C shortcut, however the problem is that content of the node is not copied.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (DROOLS-4042) [DMN Designer] Add support for importing and consuming PMML models 7.5
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-4042?page=com.atlassian.jira.plugi... ]
Michael Anstis resolved DROOLS-4042.
------------------------------------
Resolution: Done
> [DMN Designer] Add support for importing and consuming PMML models 7.5
> ----------------------------------------------------------------------
>
> Key: DROOLS-4042
> URL: https://issues.jboss.org/browse/DROOLS-4042
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Affects Versions: 7.24.0.Final
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
> Fix For: 7.24.0.Final
>
>
> We need the ability to import PMML _documents_. This should be via the "Imported models" tab. Once a _document_ has been imported (and an alias assigned) selection of the _document_ and a _model_ held therein should be possible via the PMML Function boxed expression editor.
> h2. Requirement
> - As user, via included models tab, remove included pmml model, even if used somewhere
> - As user, via included models tab, rename included pmml model, even if used somewhere
> - As user, via included models tab, include multiple pmml models
> - As user, via included models tab, include multiple pmml models at the same time eternal dmn
> - As user, via included models tab, include multiple pmml models at the same time external dmn, kinds are visually distinguished
> - As user, via dmn designer, if Document or Model of included pmml was changed, the lisboxes in dmn offers new values
> - As user, via included models tab, no restriction for included pmml model name
> - As user, via new test scenarios, test dmn model that uses pmml inside
> - As user, via kie-server, query kie container that has dmn model with pmml
> - As user, via included models tab, I want to have just unique aliases of imported models
> h2. UX design
> - Selectbox in place of Document and Model selection
> h2. Documentation
> - Mention what pmml model can be imported into dmn
> - Mention where it can be used
> - Mention if something more needed to dpeloy such project on kie server
> h2. Acceptance test
> - Include two pmml models
> - In dmn, select one in function grid
> - Change the selected one to second
> - Finish the dmn model
> - build deploy on kie-server
> - Interact with kie container via rest
> - Create new test scenario for created dmn model
> - In included models tab, try to include one pmml and one dmn with same alias, it shouldn't be possible
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (WFLY-9631) "Failed to reinstate timer" warning is shown when creating large number of EJB timers
by Ingo Weiss (Jira)
[ https://issues.jboss.org/browse/WFLY-9631?page=com.atlassian.jira.plugin.... ]
Ingo Weiss updated WFLY-9631:
-----------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/12391
> "Failed to reinstate timer" warning is shown when creating large number of EJB timers
> -------------------------------------------------------------------------------------
>
> Key: WFLY-9631
> URL: https://issues.jboss.org/browse/WFLY-9631
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 16.0.0.Final, 17.0.0.Final
> Environment: EAP 7.0.8.GA
> Oracle 12 c
> [Configuration of datasources|https://github.com/MarianMacik/timers-testing/blob/c7dde64d27...] - XA Datasource for jBPM - our application - and a separate XA Datasource for EJB Timers in a different schema.
> Reporter: Marian Macik
> Assignee: Cheng Fang
> Priority: Major
> Fix For: 18.0.0.Beta1
>
> Attachments: WFLY-9631-reproducer.zip
>
>
> Hi, [~manovotn],
> as we discussed before, I am creating a JIRA for an issue I experienced when testing EJB Timers with jBPM.
> What I did was that I started a large number of processes with jBPM, let's say 10 000 and more. Each process contains a timer which jBPM will create an EJB Timer for. Each timer was configured to fire at exactly the same time, e.g. 12:00 PM. During the test I got this warning displayed about 5 times for each 10 000 timers created:
> {code:java}
> WARN [org.jboss.as.ejb3] (Timer-1) WFLYEJB0161: Failed to reinstate timer 'kie-server.kie-server.EJBTimerScheduler' (id=09afab21-6b0f-41b0-9338-403b4a12e507) from its persistent state: java.lang.IllegalStateException: WFLYCTL0075: Duplicate resource 09afab21-6b0f-41b0-9338-403b4a12e507
> at org.jboss.as.controller.registry.AbstractModelResource$DefaultResourceProvider.register(AbstractModelResource.java:290)
> at org.jboss.as.controller.registry.AbstractModelResource.registerChild(AbstractModelResource.java:169)
> at org.jboss.as.ejb3.subsystem.deployment.TimerServiceResource.timerCreated(TimerServiceResource.java:193)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.registerTimerResource(TimerServiceImpl.java:1094)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.startTimer(TimerServiceImpl.java:767)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl$TimerRefreshListener.timerAdded(TimerServiceImpl.java:1235)
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence$RefreshTask.run(DatabaseTimerPersistence.java:820)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
> The result of these warnings was that when I had only one EAP instance to fire these timers, it wouldn't fire exactly the timers with ids that were in those warnings, e.g. if it was id=09afab21-6b0f-41b0-9338-403b4a12e507 then this timer wouldn't fire. I had waited for minutes to be sure there is another tick of a refresh interval (configured to 1 min) but nothing happened. But when I started the second EAP instance, they were immediately picked up by that instance and fired. It seems that if there is this warning on a particular instance, the instance won't pick up the timer whatsoever. They will be picked up only by some other instances if there are any. With 2 EAP instances there were warnings too, but all timers fired since I guess affected timers were picked up each time by the other instance.
> Another interesting observation is that when I configured a refresh interval to be shorter, e.g. 5 seconds, these warnings were showing up almost every 5 seconds. When I set it to 30 minutes, I didn't get warnings at all, since all timers fired earlier than a refresh occurred.
> So I think it has something to do with refresh interval.
> Can you please have a look at it? For further configuration details, check the Environment field.
> Thank you very much!
> Marian Macik
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.
by Darran Lofthouse (Jira)
[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse commented on ELY-1525:
---------------------------------------
Thinking about this further we may need to revisit how mechanisms are obtaining their request parameters - we only make use of this FormDataParser if a mechanism requires the parameters the majority of our mechanisms however only use headers so don't use the parameters.
Our FORM implementation only kicks in if a submission to j_security_check is detected so in that case it is correct we completely take over the parsing of the input stream.
The Keycloak case I believe is slightly different, I suspect it does need access to request parameters but I think the question is does it really need access to the multi part submission data in the same way a POST submission for FORM authentication would? [~pcraveiro] Do you have any thoughts on the parameter handling requirements?
Another consideration is is there a way for us to read the input stream but then reset it for subsequent servlets to be able to read it.
I think avoid reading unnecessarily is the better option but the reset if possible may be one solution.
> When SSO is enabled, multipart form and form enconding stop working.
> --------------------------------------------------------------------
>
> Key: ELY-1525
> URL: https://issues.jboss.org/browse/ELY-1525
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.6.Final, 1.2.1.Final
> Reporter: Estevão Freitas
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 1.10.0.CR3
>
> Attachments: 0001-ELY-1525-Initialize-FormParserFactory-with-FormEncod.patch, ely-1515-reproducer.zip
>
>
> I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ".
> I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On .
> When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working.
> If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months