Using a datasource name like "java:jdbc/eFpDataSource" in a persistence.xml doesn't seem to work. We seem to start to deploy the datasource but cannot resolve the service lookup.

Deploying an application that contains a persistence unit reference to the above datasource (see forum post for efp.ear zip), leads to the following server.log output:

07:20:11,374 DEBUG [org.jboss.as.connector.deployer.dsdeployer] (MSC service thread 1-1) Adding datasource: java:/java:jdbc/eFpDataSource

07:20:11,378 TRACE [org.jboss.as.naming.service.BinderService] (MSC service thread 1-2) Bound resource jdbc/eFpDataSource into naming store org.jboss.as.naming.InMemoryNamingStore@65499154

And the application (includes persistence.xml reference to EfpDataSource) fails to deploy, with the following:
New missing/unsatisfied dependencies:
service jboss.naming.context.java.java:jdbc/eFpDataSource (missing)

Instead, we should get a naming ("invalid name") exception when the datasource is added.