[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-2522:
-----------------------------------
Attachment: DROOLS-2522.mp4
> [DMN Designer] Palette aesthetics
> ---------------------------------
>
> Key: DROOLS-2522
> URL: https://issues.jboss.org/browse/DROOLS-2522
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Labels: drools-tools
> Attachments: DROOLS-2522.mp4, palette.png
>
>
> The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-9455) WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9455?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated WFLY-9455:
----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/11702
> WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
> -------------------------------------------------------------------------------------
>
> Key: WFLY-9455
> URL: https://issues.jboss.org/browse/WFLY-9455
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 11.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Fix For: 15.0.0.Alpha1
>
>
> It happens to get exception
> {code}
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction
> at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:100)
> at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1510)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> when using XTS transactions bridged to JTA for EJB handling. This happens on change of integration layer for WFTC in WFLY11.
> The integration issues were already discussed as part of the JBTM-2853.
> Here I hit a trouble of having log filled with the exception mentioned above. This does not cause a functionality trouble but the log is ugly filled with ERRORs.
> The trouble seems to be caused by the fact that transaction is imported on ivocation of WS
> https://github.com/wildfly/wildfly/blob/master/webservices/server-integra...
> but as it was suspended in the integration code before
> https://github.com/jbosstm/narayana/blob/master/txbridge/src/main/java/or...
> now the WFTC holds the notion about the transaction even on call of
> https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java...
> and such transaction is tried to be rollback which is forbidden on WFTC for imported ones and thus at least ERROR msg is written to the log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (DROOLS-2762) [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2762?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2762:
---------------------------------------
Sprint: 2018 Week 30-32, 2018 Week 36-38 (was: 2018 Week 30-32, 2018 Week 36-38, 2018 Week 39-41)
> [DMN Editor] Custom data-types - "Add row" component - this component creates new lines (in the treegrid-table)
> ---------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2762
> URL: https://issues.jboss.org/browse/DROOLS-2762
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.9.0.Final
> Reporter: Guilherme Carreiro
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DROOLS-2762.png
>
>
> The "Add component" creates new lines (in the treegrid-table) representing nested fields (in ItemDefinition):
> - This component must be disabled (or hidden) when an existing/primitive data type is selected.
> h3. Acceptance test
> - User not able to add and save lines that are filled just partially (this requirement will be addressed by the https://issues.jboss.org/browse/DROOLS-3022)
> - Added top level item definition present in output data type select box immediately (x) DROOLS-2948
> - Added item definition has structure icon if added as structure (x) DROOLS-3037
> - Check added rows after reopening (x) DROOLS-3038
> - The "Add row" button must always appear to the user (e.q. a lot of item definitions present) (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (DROOLS-2842) [DMN Designer] Recursive item definitions
by Guilherme Carreiro (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2842?page=com.atlassian.jira.plugi... ]
Guilherme Carreiro updated DROOLS-2842:
---------------------------------------
Sprint: 2018 Week 36-38 (was: 2018 Week 36-38, 2018 Week 39-41)
> [DMN Designer] Recursive item definitions
> -----------------------------------------
>
> Key: DROOLS-2842
> URL: https://issues.jboss.org/browse/DROOLS-2842
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.10.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Labels: drools-tools
> Attachments: DMCommunity Challenge - March 2017.dmn, recursive-structure-error.log
>
>
> Opening DMN model with recursive item definition inside causes unexpected error dialog with the attached error inside.
> h2. Acceptance test
> - Opening model with recursive item definition informs user with reasonable message and opens plain xml editor (/)
> - Edit data type in manage custom data type dialog that will lead to Recursive item definitions, save and reopen (/) but missing icon DROOLS-3037
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ELY-1671) Unable to build javadoc on JDK 10 and JDK 11
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1671?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1671:
-----------------------------
Description:
JDK 10 Error:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.854 s
[INFO] Finished at: 2018-09-19T13:50:48+01:00
[INFO] Final Memory: 26M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
[ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
[ERROR] are planned to be removed in a future JDK release. These
[ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
[ERROR] Users are strongly recommended to migrate to the new APIs.
[ERROR] javadoc: error - invalid flag: -Xdoclint:none
[ERROR]
[ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
JDK 11 Error:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.908 s
[INFO] Finished at: 2018-10-01T10:19:12-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - /home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/src/main/java/org/wildfly/security/manager/JDKSpecific.java:20: error: cannot find symbol
[ERROR] import sun.reflect.Reflection;
[ERROR] ^
[ERROR] symbol: class Reflection
[ERROR] location: package sun.reflect
[ERROR]
[ERROR] Command line was: /home/jucook/JDKs/Java11/OpenJDK/openjdk-11-ea+26_linux-x64_bin/jdk-11/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
was:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.854 s
[INFO] Finished at: 2018-09-19T13:50:48+01:00
[INFO] Final Memory: 26M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
[ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
[ERROR] are planned to be removed in a future JDK release. These
[ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
[ERROR] Users are strongly recommended to migrate to the new APIs.
[ERROR] javadoc: error - invalid flag: -Xdoclint:none
[ERROR]
[ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
> Unable to build javadoc on JDK 10 and JDK 11
> --------------------------------------------
>
> Key: ELY-1671
> URL: https://issues.jboss.org/browse/ELY-1671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Documentation
> Reporter: Darran Lofthouse
> Assignee: Justin Cook
> Priority: Blocker
> Fix For: 1.7.0.CR3
>
>
> JDK 10 Error:
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.854 s
> [INFO] Finished at: 2018-09-19T13:50:48+01:00
> [INFO] Final Memory: 26M/108M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
> [ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
> [ERROR] are planned to be removed in a future JDK release. These
> [ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
> [ERROR] Users are strongly recommended to migrate to the new APIs.
> [ERROR] javadoc: error - invalid flag: -Xdoclint:none
> [ERROR]
> [ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> JDK 11 Error:
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 5.908 s
> [INFO] Finished at: 2018-10-01T10:19:12-04:00
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - /home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/src/main/java/org/wildfly/security/manager/JDKSpecific.java:20: error: cannot find symbol
> [ERROR] import sun.reflect.Reflection;
> [ERROR] ^
> [ERROR] symbol: class Reflection
> [ERROR] location: package sun.reflect
> [ERROR]
> [ERROR] Command line was: /home/jucook/JDKs/Java11/OpenJDK/openjdk-11-ea+26_linux-x64_bin/jdk-11/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/jucook/Documents/WildFly/WildFly-Elytron/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (ELY-1671) Unable to build javadoc on JDK 10 and JDK 11
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/ELY-1671?page=com.atlassian.jira.plugin.s... ]
Justin Cook updated ELY-1671:
-----------------------------
Summary: Unable to build javadoc on JDK 10 and JDK 11 (was: Unable to build javadoc on JDK 10)
> Unable to build javadoc on JDK 10 and JDK 11
> --------------------------------------------
>
> Key: ELY-1671
> URL: https://issues.jboss.org/browse/ELY-1671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Documentation
> Reporter: Darran Lofthouse
> Assignee: Justin Cook
> Priority: Blocker
> Fix For: 1.7.0.CR3
>
>
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.854 s
> [INFO] Finished at: 2018-09-19T13:50:48+01:00
> [INFO] Final Memory: 26M/108M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
> [ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
> [ERROR] are planned to be removed in a future JDK release. These
> [ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
> [ERROR] Users are strongly recommended to migrate to the new APIs.
> [ERROR] javadoc: error - invalid flag: -Xdoclint:none
> [ERROR]
> [ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-10188) Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-10188?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-10188:
-----------------------------------------
[~swd847] Sorry; I didn't see this. That sounds reasonable, particularly if it was impossible (or at least quite hard) to configure a working server via the CLI in a manner that would now break. Without thinking hard the only way I think that would happen was if CLI scripts were used to recreate our existing standard configuration and the script did not set the attributes.
> Setting Undertow default server needs validation of provided server to avoid broken Wildfly configuration
> ---------------------------------------------------------------------------------------------------------
>
> Key: WFLY-10188
> URL: https://issues.jboss.org/browse/WFLY-10188
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final
> Reporter: Pavel Jelinek
> Assignee: Stuart Douglas
> Priority: Critical
>
> Undertow server needs default-host to be set to be able to be used as Undertow subsystem default-server otherwise Wildfly would not start due to:
> {code}
> ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=undertow' are not available:
> org.wildfly.undertow.host.test-server.default-host; Possible registration points for this capability:
> /subsystem=undertow/server=*/host=*
> {code}
> This is dangerous as after calling a {{reload}} operation, the server simply fails and crashes. One can accidentaly kill the server with this and \!manual\! fix is necessary to the configuration to be able to start server again.
> I think that there should be some check that configuration of the newly created server is complete and valid before it is set as a default server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months