Hi All,
Just a heads up.
I've just tested deploying an EAR with glassfish 4 because I thought I'd
try a JPA-2.1 sql inject on load setting available through the
persistence.xml that would be handy for my current dev project.
I'm currently using jumpstart's method of @EJB annotation lookup.
It deploys fine, but when loading the first page, a "Failed to detect a
known EJBProvider. Tried OpenEJB, JBoss, and GlassFish." Error message
appears.
In the EJBProviderUtil.java class, there is this
try {
Class.forName("com.sun.enterprise.admin.cli.AsadminMain");
logger.info("...found GlassFish 3.1 local.");
return EJBProviderEnum.GLASSFISH_3_1_LOCAL;
}
which sets the EJBProviderEnum to the older glassfish version.
>From a google search I found [1] this which suggests the same class exists.
The jndi name is the same for EJBs - so not really sure why it would fail
at this stage :)
Cheers
Chris
[1]
http://grepcode.com/file/repo1.maven.org$maven2@org.glassfish.admin$admin-cli@3.0-b54@com$sun$enterprise$admin$cli$AsadminMain.java
