[JBoss JIRA] (WFLY-11095) Wildfly 14.0.0 regression: EL returns empty string on constant
by Arthur Borsboom (JIRA)
[ https://issues.jboss.org/browse/WFLY-11095?page=com.atlassian.jira.plugin... ]
Arthur Borsboom commented on WFLY-11095:
----------------------------------------
Hi Jan,
The two issues are close related and I think it is smart to fix them together.
However, I do recall that the other issue was not an issue on my system when I tested Wildfly 14.
The two statements below did get resolved correctly, however the reference to a static field in a non default JRE/JDK class didn't.
Works:
foo: --- ${Boolean.TRUE} ---<br>
bar: --- ${Integer.MAX_VALUE} ---<br>
Doesn't work:
{YourConstants.FOO}
As a side note, the two Java constant statements above are a copy of my bug report for Wildfly 10 ;-)
https://developer.jboss.org/thread/271825
> Wildfly 14.0.0 regression: EL returns empty string on constant
> --------------------------------------------------------------
>
> Key: WFLY-11095
> URL: https://issues.jboss.org/browse/WFLY-11095
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.0.Final
> Environment: Linux
> Reporter: Arthur Borsboom
> Assignee: Stuart Douglas
>
> This does work in Wildfly 13, but not in Wildfly 14:
> <%@ page import="com.example.YourConstants" %>
> ${YourConstants.FOO}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jiri Ondrusek commented on WFLY-10531:
--------------------------------------
[~jwgmeligmeyling] I'll look into it.
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (WFLY-11095) Wildfly 14.0.0 regression: EL returns empty string on constant
by Jan Stourac (JIRA)
[ https://issues.jboss.org/browse/WFLY-11095?page=com.atlassian.jira.plugin... ]
Jan Stourac commented on WFLY-11095:
------------------------------------
There is already created another issue for this, see WFLY-11065. This issue has been fixed, although, there is a followup issue WFLY-11086, which has not been resolved yet.
I am gonna mark this one as a duplicate.
> Wildfly 14.0.0 regression: EL returns empty string on constant
> --------------------------------------------------------------
>
> Key: WFLY-11095
> URL: https://issues.jboss.org/browse/WFLY-11095
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.0.Final
> Environment: Linux
> Reporter: Arthur Borsboom
> Assignee: Stuart Douglas
>
> This does work in Wildfly 13, but not in Wildfly 14:
> <%@ page import="com.example.YourConstants" %>
> ${YourConstants.FOO}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Gabriele Cardosi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3053:
-------------------------------------
Description:
Implement a warning popup when the user changes the type of a column that has been already populated.
To be done *after* DROOLS-3051, because in that PR there will be implemented the "empty cell" semantic.
*Acceptance criteria*
- If the column contains no value, no confirmation is needed
- If old and new types are the same the user has to decide if the values should be removed or not
- If old and new types are not the same the user has to accept that old values will be removed
- All warning popups should contains also a "Cancel" command to abort the edit
was:
Implement a warning popup when the user changes the type of a column that has been already populated.
*Acceptance criteria*
- If the column contains no value, no confirmation is needed
- If old and new types are the same the user has to decide if the values should be removed or not
- If old and new types are not the same the user has to accept that old values will be removed
- All warning popups should contains also a "Cancel" command to abort the edit
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done *after* DROOLS-3051, because in that PR there will be implemented the "empty cell" semantic.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (DROOLS-3062) [DMN Designer] [UX] Automatic layout feature prompt
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-3062:
-----------------------------------
Summary: [DMN Designer] [UX] Automatic layout feature prompt
Key: DROOLS-3062
URL: https://issues.jboss.org/browse/DROOLS-3062
Project: Drools
Issue Type: Task
Components: DMN Editor
Reporter: Jozef Marko
Assignee: Liz Clayton
User should be able to invoke automatic layout feature anytime during diagram design phase. There should appear prompt that would explain the autolayout feature.
Please propose the the prompt.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (DROOLS-3061) [DMN Designer] Automatic Layout Feature
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-3061:
-----------------------------------
Summary: [DMN Designer] Automatic Layout Feature
Key: DROOLS-3061
URL: https://issues.jboss.org/browse/DROOLS-3061
Project: Drools
Issue Type: Epic
Components: DMN Editor
Reporter: Jozef Marko
Assignee: Daniel José dos Santos
DMN Designer should *autolayout* new imported DMN models. The *autolayout* should position DRG diagram nodes into horizontal layers to minimize crossing of connectors with respect of *Top-Down* importance. It means if nodes *Layer B* are inputs for nodes in *Layer A* then the *Layer B* will be below *Layer A*. The *autolayout* should also try to minimize scrolling needed to see whole DRG diagram.
User should also have possibility to invoke *autolayout* feature any time during designing the diagram. In this case the action should be undoable with the *Undo* toolbar button.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 2 months
[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette aesthetics
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2522:
-------------------------------------
[~manstis] Looks great to me, thank you!
> [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 (resized).png, DROOLS-2522.mp4, Screen Shot 2018-10-01 at 12.26.15 PM.png, 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