As per Appian's best practices, unlike Functions and Servlets, the initial c

The documentation says that the context that is injected will have access to the entire JNDI tree while a new InitialContext() will not. From a best practice perspective, since your plugin is running as part of a container, then it makes sense to look to the container to provide the context.

Thanks Sayed. Just 1 more query. It should go same for expression functions as well, but the documentation tells us to follow the injection mechanism for smart service and not expression function. Any specific reasons ?

The documentation does not specify but I don't believe naming context will be injected into expression functions; only the services available as part of the public API can be injected to the expression functions.