[
https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin....
]
Igor Shulika commented on WFLY-2898:
------------------------------------
Here is the debugging output for InitialContext:
final Context initContext = new InitialContext();
if (LOGGER.isDebugEnabled()) {
final Hashtable<?, ?> table = initContext.getEnvironment();
final Enumeration<?> enumKey = table.keys();
while (enumKey.hasMoreElements()) {
final Object key = enumKey.nextElement();
final Object val = table.get(key);
LOGGER.debug("InitialContext Environment: " + key + " = "
+ val);
}
}
dataSource = (DataSource) initContext.lookup(dataSourceName);
InitialContext Environment: java.naming.factory.url.pkgs =
org.jboss.as.naming.interfaces:org.jboss.ejb.client.naming
The otput the same for WFLY 8 as for JBoss EAP 6.2
JNDI Name lookup of the DataSource returns NULL
-----------------------------------------------
Key: WFLY-2898
URL:
https://issues.jboss.org/browse/WFLY-2898
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Naming, Web (Undertow)
Affects Versions: 8.0.0.CR1, 8.0.0.Final
Reporter: Igor Shulika
Assignee: Eduardo Martins
Attachments: 1.PNG, 2.PNG, 3.PNG, jaffa-oracle-driver-6.0.0.Alpha2-SNAPSHOT.jar
Hi,
I'm having a problem to obtain DataSource using JNDI Name lookup.
Please see my code below:
Connection connection = null;
DataSource dataSource = null;
try {
final Context initContext = new InitialContext();
dataSource = (DataSource) initContext.lookup("java:/MyDataSource");
connection = dataSource.getConnection();
} catch (Exception e) {
LOGGER.error(e);
}
I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP
6.2.0.GA (AS 7.3.0.Final-redhat-14).
Also I can find and test connection of my “java:/MyDataSource” under the “Datasources”
section of the WildFly Administration Console just fine(anoter word the datasource is
there).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira