[JBoss JIRA] (DROOLS-4439) [GDST] Boolean attributes are converted to XLS as numbers
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-4439?page=com.atlassian.jira.plugi... ]
Toni Rikkola updated DROOLS-4439:
---------------------------------
Parent: DROOLS-4084
Issue Type: Sub-task (was: Bug)
Steps to Reproduce: (was: # Create new guided decision table (GDST)
# Add one attribute column, choose attribute *enabled*
# Add two rows to model
# Set one as *true* second as *false*
# Click *Convert to XLS*
# Download and open xls
# The XLS will be like attached there will be *1* and *0* instead of *true* and *false*)
> [GDST] Boolean attributes are converted to XLS as numbers
> ---------------------------------------------------------
>
> Key: DROOLS-4439
> URL: https://issues.jboss.org/browse/DROOLS-4439
> Project: Drools
> Issue Type: Sub-task
> Components: Guided Decision Table Editor
> Affects Versions: 7.26.0.Final
> Reporter: Jozef Marko
> Assignee: Toni Rikkola
> Priority: Minor
> Labels: drools-tools
> Attachments: Screenshot from 2019-08-15 16-25-01.png
>
>
> Boolean attributes values are converted as integer numbers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12379) Discussion of MP compatibility guarantees in WildFly docs
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12379:
---------------------------------------
Summary: Discussion of MP compatibility guarantees in WildFly docs
Key: WFLY-12379
URL: https://issues.jboss.org/browse/WFLY-12379
Project: WildFly
Issue Type: Task
Components: Documentation
Reporter: Brian Stansberry
Assignee: Brian Stansberry
The MP specifications innovate more rapidly than EE historically has and the MP community is more willing to accept incompatible changes than EE historically has been. The result is the MP features the WF provides may change in incompatible ways between releases more frequently than typical WF features do. We should have some discussion of this in our documentation.
* The Admin Guide sections on the various MP subsystems should have some mention of this fact, focused on how output formats may change (if relevant for a spec) or how management API may change if a spec change forces an integration change that in turn requires an incompatible management API change (not expected but possible.)
* The Developer Guide should have a brief Microprofile section that highlights this fact, but focused on user API and output formats. There can be subsections for the specs we support (where we have useful content) that can provide brief further details; e.g. links to things like the MP Metrics spec changelog.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-11943) Statistics of REST endpoints
by r searls (Jira)
[ https://issues.jboss.org/browse/WFLY-11943?page=com.atlassian.jira.plugin... ]
r searls commented on WFLY-11943:
---------------------------------
Disk foot print
--without code additions
resteasy/resteasy-jaxrs: 1055195 resteasy-jaxrs-3.9.0-SNAPSHOT.jar
wildfly/jaxrs: 103976 wildfly-jaxrs-18.0.0.Beta1-SNAPSHOT.jar
--with code additions
resteasy/resteasy-jaxrs: 1060434 resteasy-jaxrs-3.9.0-SNAPSHOT.jar
wildfly/jaxrs: 115560 wildfly-jaxrs-18.0.0.Beta1-SNAPSHOT.jar
-- diff
resteasy/resteasy-jaxrs: 5239 bytes
wildfly/jaxrs: 11584 bytes
Memory Footprint (wfly console: http://localhost:9990/console runtime:status
--without code additions
wildfly:
-- Heap
used: 163 of 2048 MB
commited: 494 of 2048 MB
-- Threads
daemons: 12 of 58 threads
--with code additions
wildfly:
-- Heap
used: 153 of 2048 MB
commited: 494 of 2048 MB
-- Threads
daemons: 12 of 58 threads
> Statistics of REST endpoints
> ----------------------------
>
> Key: WFLY-11943
> URL: https://issues.jboss.org/browse/WFLY-11943
> Project: WildFly
> Issue Type: Feature Request
> Components: REST
> Affects Versions: 17.0.0.Final
> Reporter: r searls
> Assignee: r searls
> Priority: Major
> Labels: affects-model
> Fix For: 18.0.0.Beta1
>
>
> Provide statistics on REST endpoints in the jaxrs subsystem.
> CLI support "read-resource" operation for jax-rs subsystem in deployment:
> /deployment=jaxrs-eap.war/subsystem=jaxrs:read-resource
> Statistics should be added to results of this operation in this RFE.
> There needs to be option to enable or disable collecting of these statistics, because collecting of statistics does probably some performance drop.
> The change of statistic settings should not require server reload or restart.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months