[JBoss JIRA] (DROOLS-3565) DMN: Navigator panel UX updates
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3565?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3565:
--------------------------------
Sprint: (was: 2019 Week 05-07)
> DMN: Navigator panel UX updates
> -------------------------------
>
> Key: DROOLS-3565
> URL: https://issues.jboss.org/browse/DROOLS-3565
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UXTeam, drools-tools
> Attachments: Screen Shot 2019-01-28 at 1.38.21 PM.png, Screen Shot 2019-01-28 at 2.35.00 PM.png, Screen Shot 2019-01-31 at 9.45.39 AM.png, Screen Shot 2019-02-01 at 10.52.51 AM.png
>
>
> As a user I want to be able to be able to view and use imported nodes and decision logic in the diagram that I am authoring.
> Based on card view design (see linked jira), detail new Navigator elements required to support this workflow including:
> - Import components panel: Filter components by BKMs, decisions..., badge count
> - Graph panel with checkbox option to view map.
> - Single scrolling navigator.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11661) async-handler not working / logging.properties incompletely updated
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11661?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-11661:
---------------------------------------
Component/s: Logging
Assignee: James Perkins (was: Brian Stansberry)
> async-handler not working / logging.properties incompletely updated
> -------------------------------------------------------------------
>
> Key: WFLY-11661
> URL: https://issues.jboss.org/browse/WFLY-11661
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Affects Versions: 10.1.0.Final, 11.0.0.Final
> Reporter: Marco Schulze
> Assignee: James Perkins
> Priority: Major
>
> The {{logging.properties}} file which is generated from the {{standalone.xml}} is not correctly updated. When switching to asynchronous logging by renaming the {{"FILE"}} handler to {{"FILE.sync"}} and then introducing an {{async-handler}} named {{"FILE"}} referencing {{"FILE.sync"}} in its {{subhandlers}}, the {{logging.properties}} then lacks the following line:
> {quote}handler.FILE.handlers=FILE.sync{quote}
> I tested this with WildFly 10 and 11, but this bug might affect more (and newer) versions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (DROOLS-2728) UX for custom data-types
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ]
Liz Clayton resolved DROOLS-2728.
---------------------------------
Resolution: Done
[~karreiro][~tirelli] Marking as resolved because designs have been delivered. Iterations will be covered in separate jiras.
> UX for custom data-types
> ------------------------
>
> Key: DROOLS-2728
> URL: https://issues.jboss.org/browse/DROOLS-2728
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: UX, UXTeam, drools-tools
> Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png
>
>
> As a practitioner I want to be able to:
> * select an existing data type
> * create a simple or structured data type
> * create a “compound” (or complex) data type, easily.
> *
expand/collapse views of compound data types, so that I can___
> *
navigate between levels in a compound data type, so that I can___
> * edit an existing data type
> * remove an existing data type
>
…so that I can use the data type when creating a decision related asset.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11717) Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11717?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11717:
-----------------------------------------
[~krisgerhard] Can you provide more information on where/when you are seeing this? My presumption is the source of the complaint is [1] (that's the anonymous inner class in AbstractProxyFactory) but I'm not seeing why that would be invoked for Object.clone().
[1] https://github.com/jbossas/jboss-invocation/blob/master/src/main/java/org...
> Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
> ---------------------------------------------------------------------------
>
> Key: WFLY-11717
> URL: https://issues.jboss.org/browse/WFLY-11717
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 15.0.1.Final
> Reporter: Kris-Gerhard Aabrams
> Assignee: Brian Stansberry
> Priority: Major
> Labels: Java11
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/opt/jboss/wildfly/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.1.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> 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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11728) Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.
by Andrej Petras (Jira)
Andrej Petras created WFLY-11728:
------------------------------------
Summary: Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.
Key: WFLY-11728
URL: https://issues.jboss.org/browse/WFLY-11728
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 15.0.1.Final
Reporter: Andrej Petras
Assignee: Alessio Soldano
09:35:25,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: Failed to start service
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]
at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.Validator.validateBeanName(Validator.java:653)
at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:121)
at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:119)
at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
09:35:25,941 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mp-client-1.0.0-SNAPSHOT.war\".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]"}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (ELY-1756) Fix org.wildfly.security.tool.FileSystemRealmCommandTest failure on Windows
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1756?page=com.atlassian.jira.plugin.s... ]
Farah Juma reassigned ELY-1756:
-------------------------------
Assignee: Justin Cook
> Fix org.wildfly.security.tool.FileSystemRealmCommandTest failure on Windows
> ---------------------------------------------------------------------------
>
> Key: ELY-1756
> URL: https://issues.jboss.org/browse/ELY-1756
> Project: WildFly Elytron
> Issue Type: Task
> Components: Testsuite
> Reporter: Farah Juma
> Assignee: Justin Cook
> Priority: Critical
> Fix For: 1.9.0.CR1, 2.0.0.Alpha2
>
>
> The {{org.wildfly.security.tool.FileSystemRealmCommandTest}} is currently failing on Windows for the 1.x and master Elytron branches:
> {code}
> ======= Failed test run #1 ==========
> java.lang.ExceptionInInitializerError
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> Caused by: java.nio.file.InvalidPathException: Illegal char <:> at index 2: /C:/buildAgent/work/47c7d1a7a2ffc4ef/tool/target/test-classes/
> at java.base/sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> at java.base/sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> at java.base/sun.nio.fs.WindowsPath.parse(WindowsPath.java:92)
> at java.base/sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:229)
> at java.base/java.nio.file.Path.of(Path.java:147)
> at java.base/java.nio.file.Paths.get(Paths.java:69)
> at org.wildfly.security.tool.FileSystemRealmCommandTest.<clinit>(FileSystemRealmCommandTest.java:62)
> ... 17 more
> ======= Failed test run #2 ==========
> java.lang.NoClassDefFoundError: Could not initialize class org.wildfly.security.tool.FileSystemRealmCommandTest
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11717) Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11717?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFLY-11717:
------------------------------------
Labels: Java11 (was: )
> Illegal reflective access - org.jboss.invocation.proxy.AbstractProxyFactory
> ---------------------------------------------------------------------------
>
> Key: WFLY-11717
> URL: https://issues.jboss.org/browse/WFLY-11717
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 15.0.1.Final
> Reporter: Kris-Gerhard Aabrams
> Assignee: Brian Stansberry
> Priority: Major
> Labels: Java11
>
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/opt/jboss/wildfly/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.1.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> 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
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 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] [~tirelli] fyi, please edit as needed. I made this principally for the UX work, but could be multi-purpose.
> 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)
7 years, 2 months