jgitter的回答给了我最大的方式。这是我结束了:
/**
* @return a reference to the EJB
* @throws EjbLookupException
*/
@NotNull
public T lookup()
throws EjbLookupException
{
String path = createJndiPath();
Context initialContext = null;
try
{
initialContext = createInitialContext();
//noinspection unchecked
final T ejb = (T)initialContext.lookup(path);
if(m_apiVersion != null)
{
((RemoteAPI)ejb).validateClientCompatibility(m_apiVersion);
}
return ejb;
}
catch(NamingException | RuntimeException e)
{
throw new EjbLookupException("Unable to find the JBoss EJB at " + path, e);
}
finally
{
if(initialContext != null)
{
//noinspection ThrowableResultOfMethodCallIgnored
Closer.close(initialContext);
}
}
}
/**
* There are a lot of ways to do JBoss 7/Wildfly EJB lookups. Using this method, we don't have to create
* outbound socket bindings whenever we want to use a remote EJB.
*
* @throws NamingException
*/
@NotNull
private Context createInitialContext()
throws NamingException
{
Properties properties = new Properties();
properties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
properties.put("org.jboss.ejb.client.scoped.context", "true");
properties.put("remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED", "false");
properties.put("remote.connection.default.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS", "false");
properties.put("remote.connections", "default");
properties.put("remote.connection.default.host", m_host);
properties.put("remote.connection.default.port", String.valueOf(m_port));
if(m_username != null)
{
properties.put("remote.connection.default.username", m_username);
}
if(m_password != null)
{
properties.put("remote.connection.default.password", m_password);
}
return new InitialContext(properties);
}
public static class EjbLookupException
extends Exception
{
EjbLookupException (
@NotNull String message,
@NotNull Throwable cause)
{
super(message, cause);
}
}
我不知道如果我需要一个scoped context,我可能无法正确关闭连接。我会根据我的发现更新这个答案。
当你在wildly而不是tomcat中使用相同的代码时会发生什么? –
您是否知道您可以为您的Ops团队提供一个六行CLI脚本,它将为您设置远程出站连接?这有利于将远程主机配置与应用程序完全分开。只是别的可以考虑... –
在蜻蜓工作的代码生成的“EJB客户端上下文选择器可能不会改变”在蜻蜓 –