A bean in each ear .....

Hi,
We've developed a grand app using OC4J. The app consists of two ears, both deployed in the same oc4j, one may be moved to a separate server at some stage. When deployed locally the structure in the container root is ....
(the xml files are in META-INF in each case)

bean2.ear
-------- bean2-ejb.jar
-----------ejb-jar.xml

bean1.ear
--------webapp
--------bean1-ejb.jar
--------------ejb-jar.xml
--------------application-client.xml

bean1 accesses bean2 by doing a lookup on ormi://localhost/bean2
there is no <ejb-ref> to bean2 in bean1's ejb-jar.xml, The <ejb-ref> stuff is in application-client.xml

bean2 ejb-jar.xml has no ref to bean1 - because it is a client

when deployed on 10gAS , we get an error saying that bean1 can't find bean2 -it can't read the application-client descriptor ( which is where it should be)
So, the big question what are we doing wrong? Is this the correct config or have we missed a trick somewhere? As I said it all works fine in OC4j standalone so summat must be right

Cheers

I don't think I understand why you have two EAR files. It looks as if there is one deployment unit, so include the client application in a single EAR file.

because bean2 will be deployed on another server eventually and probably accessed by other clients for other purposes , and, although I had initially built them in the same ear it was considered pertinent to split em up

[ July 13, 2005: Message edited by: Mike Halford ]