[JBoss JIRA] (DROOLS-3154) Minor UI improvements/bugfixes for Scenario
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3154?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-3154:
--------------------------------
Labels: UX-CSS (was: )
> Minor UI improvements/bugfixes for Scenario
> -------------------------------------------
>
> Key: DROOLS-3154
> URL: https://issues.jboss.org/browse/DROOLS-3154
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Critical
> Labels: UX-CSS
>
> This item contains a list of general UI bugs to be fixed:
> - Use grey borders for all the grid and not only for the header
> - Add some padding to the cells of the grid
> - Add some padding to right panel the tab titles
> - Remove scrolling bar from right panel
> - Review expression editor component HTML/CSS (paddings, indents, etc)
> - Review right panel padding (now it is hardcoded)
> - Use text area inputs instead of text box for inline editing
> - Reduce the width of Index column
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFCORE-4171) vault launchers should not be part of core feature-pack
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFCORE-4171?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-4171:
------------------------------------------
Perhaps they can go in servlet feature pack.
Fundamentally this uses VaultTool, which is in the org.jboss.as.security module, which is in servlet feature pack.
The script calls the org.jboss.as.vault-tool which is only in full feature pack. That module is just a module.xml though, pointing at org.jboss.as.security. It bring no new classloading dependencies so there's no great technical reason for it to be restricted to full.
[~jdenise] Perhaps this should be addressed in the context of working out what a 'vault layer' would look like.
> vault launchers should not be part of core feature-pack
> -------------------------------------------------------
>
> Key: WFCORE-4171
> URL: https://issues.jboss.org/browse/WFCORE-4171
> Project: WildFly Core
> Issue Type: Bug
> Components: Scripts
> Reporter: Jean-Francois Denise
> Priority: Major
>
> They should be moved to wildfly full feature-pack
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (AG-99) Enforce setting "max size"
by Luis Barreiro (Jira)
Luis Barreiro created AG-99:
-------------------------------
Summary: Enforce setting "max size"
Key: AG-99
URL: https://issues.jboss.org/browse/AG-99
Project: Agroal
Issue Type: Bug
Components: api
Affects Versions: 1.2
Reporter: Luis Barreiro
Assignee: Luis Barreiro
Fix For: 1.3
The default value for {{maxSize}} is {{java.lang.Integer#MAX_VALUE}} which can lead to the database rejecting connections (for apparently no good reason).
The {{maxSize}} attribute should be made mandatory.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months