Each deployed war and ejb-jar is treated as a separate application even
if they are deployed in the same instance. Only EJBs with remote
interface can be accessed from other applications. So, your EJBs must
have remote interfaces. To solve the class not found exception, you have
to duplicate the ejb remote interfaces and their dependencies in each
war file. This is a portable approach.
Thanks,
Sahoo
glassfish_at_javadesktop.org wrote:
> Hi,
>
> I need to know if this is possible:
>
> 1. -Deploy a EJB component to GlassFish with several session beans an entity beans
> and
> 2.- Deploy a web application that will use the Beans previously deployed in the standalone EJB component.
>
> I explain:
> Right know I am able to ensamble a EAR application with both EJB and WAR components, everything works fine. But my EJB component will be used by several web applications, so I do not want to create severa EAR projects all using the same ejb component.
>
> I want to deploy only one EJB component to GlassFish and then be able to deploy several WEB application that all will use the same EJB Component.
>
> I have deployed the standalone EJB component without errors. When I try to deploy the war file of the web application I get a classNotFound exception for the interface class name . I am not able to use JNDI correctly.
>
> Thank you for your help.
>
> Antonio
> [Message sent by forum member 'antoniojsg' (antoniojsg)]
>
> http://forums.java.net/jive/thread.jspa?messageID=294543
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>