[jboss-jira] [JBoss JIRA] (WFLY-11963) ejb3 thread-pool thread-factory should be shown deprecated in management api

[Chao Wang (Jira)]

    [ https://issues.redhat.com/browse/WFLY-11963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956735#comment-13956735 ] 

Chao Wang commented on WFLY-11963:
----------------------------------

[~mshikalw] No, I am not. You can take it. Thanks.

> ejb3 thread-pool thread-factory should be shown deprecated in management api
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-11963
>                 URL: https://issues.redhat.com/browse/WFLY-11963
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 16.0.0.Final
>            Reporter: Chao Wang
>            Priority: Major
>
> ejb3 thread-pool thread-factory should be shown deprecated in management api
> The threads subsystem was deprecated and is not in the EAP 7.x configurations, so the thread-factory attribute on the ejb3 thread-pool configuration should indicate it is deprecated and should not be used.
> {code}
> /subsystem=ejb3/thread-pool=default:read-resource-description(
>             "thread-factory" => {
>                 "type" => STRING,
>                 "description" => "Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.",
>                 "expressions-allowed" => false,
>                 "required" => false,
>                 "nillable" => true,
>                 "min-length" => 1L,
>                 "max-length" => 2147483647L,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "all-services"
>             }
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)