Can you tell how you have packaged both the ear files?
Have you successfully deployed the ear file that contains ABSessionBean?
Was there any warning in log file? If ABSessionBean does not appear in
JNDI tree, then you should investigate that first before deploying the
second ear file.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> Sorry, I failed to mention the Error Message I get from asadmin when trying to deploy XYSessionBean: it says CLI171 followed by a german message saying that the EjbDescriptor could not be processed.
>
> The client view class of ABSessionBean (ABSession) is packaged with XYSessionBean.
>
> Something else is odd: when trying to browse the JNDI tree in the admin console, ABSessionBean does not appear. I have not specified a deployment descriptor or anything else, just the remote interfaces and bean classes I have described above, plus a manifest.mf in each EAR.
>
> Thanks for your help
>
> Michael
> [Message sent by forum member 'mschwind' (mschwind)]
>
> http://forums.java.net/jive/thread.jspa?messageID=328643
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>