Don't know if this will help, but it looks like the problem starts
with the execution of a finder query. So maybe review the sql you've set
for this query in orion-ejb-jar.xml.
Or maybe the query can return more than one row and you have it set to
return
a single entity instance in the ejb's home
I originally posted this at elephantwalker but have had little response,
hopefully someone here has some ideas...
I'm trying to lookup a bean on a remote machine. I set up initial context in
usual way using properties taken from the jndi.properties on the remote oc4j
server.
In fact I want to
I was looking for a config problem!
OK now I'm ashamed.
Thanks though, I have been overlooking that for days.
-Original Message-
From: Alex Paransky [mailto:[EMAIL PROTECTED]]
Sent: 23 January 2002 21:41
To: Chris Francis; Orion-Interest
Subject: RE: javax.naming.NameNotFoundException
Err, I haven't spammed this several times to the list! There must be
something up at the list server.
Apologies.
Chris.
-Original Message-
From: Chris Francis [mailto:[EMAIL PROTECTED]]
Sent: 23 January 2002 12:39
To: Orion-Interest
Cc: Chris Francis
Subject: RE
Hi All,
I'm tearing my hair out trying to get this to work.
I have a couple of entity beans and a session bean.
Everything deploys OK. The session needs to access the
two entities. I've seen the examples but they look to be
the same as what I've got. The ejb's are not in a jar but
all live in
need to) ?
WR
-Ursprungligt meddelande-
Från: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]För Chris Francis
Skickat: den 22 januari 2002 12:21
Till: Orion-Interest
Ämne: FW: javax.naming.NameNotFoundException
Hi All,
I'm tearing my hair out trying to get this to work.
I have
