How to configure bc4j.xcfg ConnectionDefinition to JBoss 3.2.3?

Question

Hi,
we have the following scenario here: a JClient for BC4J goes via Web Start
and tries to communicate back to the AppModule deployed in JBoss 3.2.3 as
Session Bean (BMT).
We are using JDev 9.0.4.
How can we configure the element <ConnectionDefinition> in common\bc4j.xcfg
file in order to lookup the AppModule at JBoss?
We were able to set up this scenario working in OC4J, but we are in trouble
with JBoss.
How can we change the following connection so it points to a JBoss app server?
<ConnectionDefinition name="MyConnection">
<ENTRY name="URL" value="ormi://myserver/"/>
<ENTRY name="ConnectionName" value="MyConnection"/>
<ENTRY name="user" value="admin"/>
<ENTRY name="ConnectionType" value="OC4J"/>
<ENTRY name="password">
<![CDATA[{904}05E438994FF93]]>
</ENTRY>
<ENTRY name="JNDI_INITIAL_CONTEXT_FACTORY" value="com.evermind.server.rmi.RMIInitialContextFactory"/>
<ENTRY name="DeployPassword" value="true"/>
<ENTRY name="TARGET_NODE" value="http-web-site"/>
<ENTRY name="DeployPassword" value="true"/>
</ConnectionDefinition>
Maybe it should look like this?
<ConnectionDefinition name="MyConnection">
<ENTRY name="URL" value="jnp://myserver:1099"/>
<ENTRY name="ConnectionName" value="MyConnection"/>
<ENTRY name="ConnectionType" value="JBoss"/>
<ENTRY name="JNDI_INITIAL_CONTEXT_FACTORY" value="org.jnp.interfaces.NamingContextFactory"/>
<ENTRY name="JNDI_URL_PKG_PREFIXES" value="org.jboss.naming:org.jnp.interfaces"/>
</ConnectionDefinition>
Hope somebody can help us.
Eduardo.

Answer 1

Frank,
the reason we didn't deployed BC4J as a Web application is we weren't given options. Our contractor wanted a 3-tier application with rich client (JClient/Swing), an load-balanced application server and a legacy database at back end.
The problem with the article "How Do I Deploy BC4J Applications to JBoss?" is that it doesn't mention how to configure common\bc4j.xcfg in order to connect with JBoss app server.
The connection with the data source is ok.
But how come the client would be able to lookup Remote Home interfaces through JNDI without knowing the protocol, host, port number and initial context properties specific to JBoss?
Thanks,
Eduardo.