]
Michal Petrov commented on WFLY-13697:
--------------------------------------
[~jdenise], how does CLI talk to WidlFly? What is happening here is that the quickstart
webapp creates a {{HttpServerExchange}} and Undertow will
push {{InjectedEENamespaceContextSelector}} into {{NamespaceContextSelector}}. But with
CLI this doesn't happen and {{NamespaceContextSelector}} will return the default
selector (from {{DefaultNamespaceContextSelectorService}}) which cannot resolve
"java:app".
JBoss CLI can't find java:app/AppName
-------------------------------------
Key: WFLY-13697
URL:
https://issues.redhat.com/browse/WFLY-13697
Project: WildFly
Issue Type: Bug
Components: CLI
Affects Versions: JBoss AS7 7.2.0.Final
Reporter: José Fernando Tepedino Martins
Assignee: Jean Francois Denise
Priority: Minor
Labels: CLI, JNDI
With a JEE aplication in a WAR package, when starting a functionality, as a Batch Job,
via CLI, CDI injection and JNDI lookup fail to find resources 'java:app/AppName'
and 'java:module/ModuleName'.
For example, a job listener or other job artifact with the following code
{code:java}
@Resource(lookup="java:app/AppName")
private String applicationName;{code}
or
{code:java}
private String applicationName;
@PostConstruct
protected void initialize() throws NamingException {
applicationName = InitialContext.doLookup("java:app/AppName");
}{code}
when the batch job is started from JBoss CLI, the following error will be logged:
{code:java}
javax.naming.NameNotFoundException: java:app/AppName
{code}