[JBoss JIRA] (DROOLS-3567) Import tab, with cards.
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3567:
------------------------------------------
[~uxdlc], [~karreiro], sorry for the delay. That works for me. I'd just tweak a bit:
{quote}
No DMN models have been included.
There are currently no DMN models included within this DMN model. To get started, click *Include model*.
{quote}
Not a fan of the repetition, but clearer. I'm open to other suggestions. Also, we might want to update the data types message to say "To get started, click *Add*." for consistency.
> Import tab, with cards.
> -----------------------
>
> Key: DROOLS-3567
> URL: https://issues.jboss.org/browse/DROOLS-3567
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UXTeam, drools-tools
> Attachments: 3.png, Import-tab.pdf
>
>
> Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999
> Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3567) Import tab, with cards.
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3567?page=com.atlassian.jira.plugi... ]
Stetson Robinson edited comment on DROOLS-3567 at 2/26/19 1:44 PM:
-------------------------------------------------------------------
[~uxdlc], [~karreiro], sorry for the delay. That works for me. I'd just tweak a bit:
{quote}
*No DMN models have been included.*
There are currently no DMN models included within this DMN model. To get started, click *Include model*.
{quote}
Not a fan of the repetition, but clearer. I'm open to other suggestions. Also, we might want to update the data types message to say "To get started, click *Add*." for consistency.
was (Author: stetson.robinson):
[~uxdlc], [~karreiro], sorry for the delay. That works for me. I'd just tweak a bit:
{quote}
No DMN models have been included.
There are currently no DMN models included within this DMN model. To get started, click *Include model*.
{quote}
Not a fan of the repetition, but clearer. I'm open to other suggestions. Also, we might want to update the data types message to say "To get started, click *Add*." for consistency.
> Import tab, with cards.
> -----------------------
>
> Key: DROOLS-3567
> URL: https://issues.jboss.org/browse/DROOLS-3567
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UXTeam, drools-tools
> Attachments: 3.png, Import-tab.pdf
>
>
> Detail Import design as presented in: https://issues.jboss.org/browse/DROOLS-2999
> Specify any details not already covered by the patternfly card pattern: https://www.patternfly.org/pattern-library/content-views/card-view/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Cheng Fang resolved WFLY-11720.
-------------------------------
Resolution: Explained
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Assignee: Cheng Fang
> Priority: Critical
> Attachments: classes.zip, client-app.zip
>
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports
by Tiago Dolphine (Jira)
[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ]
Tiago Dolphine commented on DROOLS-3659:
----------------------------------------
[~uxdlc] yes, the documentation is based on an html template, for BPMN the template that is here https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-stunn..., probably this could be copied to DMN and changed to the DMN needs.
The necessary work for DMN is to implement a service that should generate the documentation model that is going to be used with the template to fill the variables. I can help with this when the issue starts to be developed. But all the other stuff like the Documentation Tab, template engine, etc can be reused in the same way as for BPMN, because they are located on the common stunner modules not specific to BPMN.
> DMN: UX for documentation reports
> ---------------------------------
>
> Key: DROOLS-3659
> URL: https://issues.jboss.org/browse/DROOLS-3659
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> User stories:
> * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file.
> * As a user I need a means through the UI to input additional documentation, links and attachments to nodes.
> Notes:
> - Docs to help with docs formatting.
> - Might be able to leverage Case View docs widget.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3659:
-------------------------------------
[~stetson.robinson] Nice! [~tdolphine] Would you be able to use the same layout/formatting?
> DMN: UX for documentation reports
> ---------------------------------
>
> Key: DROOLS-3659
> URL: https://issues.jboss.org/browse/DROOLS-3659
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> User stories:
> * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file.
> * As a user I need a means through the UI to input additional documentation, links and attachments to nodes.
> Notes:
> - Docs to help with docs formatting.
> - Might be able to leverage Case View docs widget.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3659:
---------------------------------------
+1, looks good [~stetson.robinson]
> DMN: UX for documentation reports
> ---------------------------------
>
> Key: DROOLS-3659
> URL: https://issues.jboss.org/browse/DROOLS-3659
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> User stories:
> * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file.
> * As a user I need a means through the UI to input additional documentation, links and attachments to nodes.
> Notes:
> - Docs to help with docs formatting.
> - Might be able to leverage Case View docs widget.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (DROOLS-3659) DMN: UX for documentation reports
by Stetson Robinson (Jira)
[ https://issues.jboss.org/browse/DROOLS-3659?page=com.atlassian.jira.plugi... ]
Stetson Robinson commented on DROOLS-3659:
------------------------------------------
[~tirelli], [~uxdlc], here's my stab at an [example DMN model report|https://docs.google.com/document/d/1xZBnRQfaTpFmMjU11Wzc2HhBqJCOVK...]. It's similar to what Trisotech does, with some cleaner and different components. I looked through various sample DRD and DMN file properties to see what sorts of things make sense to include in a report. The meat of it is really just the DRD components and their respective elements.
Feel free to tweak, add to, or comment on the example report.
> DMN: UX for documentation reports
> ---------------------------------
>
> Key: DROOLS-3659
> URL: https://issues.jboss.org/browse/DROOLS-3659
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
>
> User stories:
> * As a user I want to generate a PDF or HTML report of the DMN model, with documentation, so that I can hand it off to external team and/or business that needs information about the diagrams and the logic of the decisions being automated. The report can be printed out and used by business teams not involved with the modeling itself, to learn about content of the .dmn file.
> * As a user I need a means through the UI to input additional documentation, links and attachments to nodes.
> Notes:
> - Docs to help with docs formatting.
> - Might be able to leverage Case View docs widget.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months