[
https://issues.jboss.org/browse/WFCORE-2895?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-2895:
-------------------------------------
Description:
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates
it's ServiceName by parsing the base capability's string name instead of using its
existing ServiceName. This wastes memory since the strings end up being duplicated.
Also RuntimeCapability should not create a ServiceName even if the cap has no
serviceValueType.
was:
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates
it's ServiceName by parsing the base capability's string name instead of using its
existing ServiceName. This wastes memory since the strings end up being duplicated.
As a side task look into why we create a ServiceName even if the cap has no
serviceValueType.
Save memory in dynamic RuntimeCapability ServiceName creation
-------------------------------------------------------------
Key: WFCORE-2895
URL:
https://issues.jboss.org/browse/WFCORE-2895
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
RuntimeCapability.fromBaseCapability results in a new RuntimeCapability that creates
it's ServiceName by parsing the base capability's string name instead of using its
existing ServiceName. This wastes memory since the strings end up being duplicated.
Also RuntimeCapability should not create a ServiceName even if the cap has no
serviceValueType.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)