[
https://issues.redhat.com/browse/WFLY-13809?page=com.atlassian.jira.plugi...
]
Cheng Fang updated WFLY-13809:
------------------------------
Description:
AbstractJobOperator currently gets application name via jndi lookup. It is an expensive
operation for this task. Also in non-EE environment, lookup of application name will
always return null. So it is better to retrieve application name from
{{BatchEnvironment}}, and different impl of {{BatchEnvironment}} can provide application
name differently.
Need to adjust {{BatchEnvironmentService}} to provide application name.
was:AbstractJobOperator currently gets application name via jndi lookup. It is an
expensive operation for this task. Also in non-EE environment, lookup of application name
will always return null. So it is better to retrieve application name from
{{BatchEnvironment}}, and different impl of {{BatchEnvironment}} can provide application
name differently.
Get application name from BatchEnvironment instead of jndi lookup
-----------------------------------------------------------------
Key: WFLY-13809
URL:
https://issues.redhat.com/browse/WFLY-13809
Project: WildFly
Issue Type: Enhancement
Components: Batch
Affects Versions: 20.0.1.Final
Reporter: Cheng Fang
Assignee: Cheng Fang
Priority: Major
AbstractJobOperator currently gets application name via jndi lookup. It is an expensive
operation for this task. Also in non-EE environment, lookup of application name will
always return null. So it is better to retrieve application name from
{{BatchEnvironment}}, and different impl of {{BatchEnvironment}} can provide application
name differently.
Need to adjust {{BatchEnvironmentService}} to provide application name.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)