这开始让我彻底发疯......
我想使用 Maven 创建一个 Glassfish 客户端应用程序。
为此,我添加了所需的 gf-client 依赖项:
<dependency>
<groupId>org.glassfish.appclient</groupId>
<artifactId>gf-client</artifactId>
<version>3.1</version>
<type>pom</type>
<scope>compile</scope>
</dependency>
然后,想要联系在同一应用程序上运行的 Glassfish 服务器,我会进行常规查找:
Properties p = new Properties();
// optional. Defaults to localhost. Only needed if web server is running
// on a different host than the appserver
p.setProperty("org.omg.CORBA.ORBInitialHost", "localhost");
// optional. Defaults to 3700. Only needed if target orb port is not
// 3700.
p.setProperty("org.omg.CORBA.ORBInitialPort", "3700");
Context context = new InitialContext(p);
// Stores the list of reachable EJBs
return context.lookup(interfacesToNames.getProperty(className));
不幸的是,当这样做时,我得到的只是
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.enterprise.naming.impl.SerialInitContextFactory [Root exception is java.lang.ClassNotFoundException: com/sun/enterprise/naming/impl/SerialInitContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
... 6 more
Caused by: java.lang.ClassNotFoundException: com/sun/enterprise/naming/impl/SerialInitContextFactory
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:63)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
... 9 more
经过一番检查后,我注意到我的glassfish-naming-3.1.jar
存在于该客户端应用程序的 CLASSPATH 中。并且,根据 Eclipse 代码查找,这个 jar 应该包含com.sun.enterprise.naming.impl.SerialInitContextFactory
。但是,如果在调试模式下,我会这样做getClass().getClassLoader().getResource("com/sun/enterprise/naming/impl/SerialInitContextFactory")
它返回 null,这清楚地表明找不到该类。
有关更多信息,JAR 是使用此插件配置从我的本地 Maven 存储库复制的:
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>package output directory</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<prependGroupId>true</prependGroupId>
<includeScope>compile</includeScope>
<outputDirectory>${dependencies.outputDir}/jars</outputDirectory>
<prefix>${dependencies.outputDir}</prefix>
</configuration>
</execution>
</executions>
</plugin>
此外,我必须承认,当使用相同的 API 连接到 Glassfish 服务器运行简单测试时,绝对没有问题,这将我引向了 ClassLoader 问题。
运行该客户端时,当前的类加载器是(如getClass().getClassLoader().getClass().getName()
) sun.misc.Launcher$AppClassLoader
。不幸的是,这与运行单元测试时完全相同。
那么,我能做些什么来解决这个错误呢?
EDIT类存在于glassfish-naming-3.1.jar
,但标准类加载器似乎找不到。
EDIT一个有趣的发现:
getClass().getClassLoader().getResource("com/sun/enterprise/naming/impl") = jar:file:/C:/Users/pouet/pouet/target/jars/glassfish-naming-3.1.jar!/com/sun/enterprise/naming/impl
while
getClass().getClassLoader().getResource("com/sun/enterprise/naming/impl/SerialInitContextFactory") = null