Are you using JDK 1.3? If not, you need the iioprt.jar file from the
1.3 JDK in your classpath.
At least that's what I'm guessing is the problem. In SP2, soon to be
released, we'll ship iiioprt.jar in JRun's lib/ext dir. This file has
the RMI-IIOP classes in it that are needed for
PortableRemoteObject.narrow().
On the other hand, it may be something else. I'll be glad to help with
it. Take my advice -- stick with the ejb-jar.xml and forget the
properties files. You'll notice that none of the sample clients with
JRun use the PortableRemoteObject method of getting a home object. One
of the samples in SP2 will though.
--
Scott Stirling
West Newton, MA
On 04 Jan 2001 09:34:41 -0500, Usha Chintalapati wrote:
> I'm having trouble understanding, which parts of the EJBean.properties file
> registers the JNDI name for that bean. I followed the directions given in
> samples.pdf, but they didn't work.
>
> I tried deploying the beans both ways, using the deployment descriptor
> ejb-jar.xml and using properties files with manifest file. If anyone has
> encountered similar problems and found a solution, I would really appreciate
> it if you can let me know.
>
> TIA,
> Usha
>
> Below are excerpts of configuration files and my code.
>
> Deploying using ejb-jar.xml:
> - Here's how I defined a bean in this file:
> <session>
> <ejb-name>XXXHome</ejb-name>
> <home>com.synapz.eclipz.ejb.XXXHome</home>
> <remote>com.synapz.eclipz.ejb.XXX</remote>
> <ejb-class>com.synapz.eclipz.ejb.XXXBean</ejb-class>
> <session-type>Stateless</session-type>
> <transaction-type>Container</transaction-type>
> <env-entry>
> <env-entry-name>ejipt.isCreateSilent</env-entry-name>
> <env-entry-value>true</env-entry-value>
> </env-entry>
> </session>
> - In my client code, I lookup this bean the following way:
> void someMethod()
> {
> System.setProperty(Context.INITIAL_CONTEXT_FACTORY,
> "allaire.ejipt.ContextFactory");
> System.setProperty(Context.PROVIDER_URL,
> "ejipt://localhost:2323");
>
> Context ctx = getInitialContext();
>
> Object home = ctx.lookup("XXXHome");
>
> XXXHome xxxHome =
> (XXXHome) javax.rmi.PortableRemoteObject
> .narrow(home, XXXHome.class);
> }
> - I do not have any problem deploying my ejb jar or my client jar. However,
> when I run my client code I get the following error:
> javax.naming.NameNotFoundException: UserHandlerHome not found
> at allaire.ejipt._NamingContext.lookup(_NamingContext.java:73)
> at allaire.ejipt._ClientContext.lookup(_ClientContext.java:113)
> at javax.naming.InitialContext.lookup(InitialContext.java:350)
> .........
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
