about "client view jar file must be included directly in app2.ear file"

[Himai Minh]

Hi,
On p.594 of JSR-318,

Note that client view jar file must be included directly in the app2.ear file.

app1.ear
  ejb1.jar
  ejb1_client.jar
  ejb2.jar
app2.ear:
   META-INF/application.xml
   ejb1_client.jar   //This ejb1_client.jar must be in app2.ear in order to be accessed from ejb3.jar ?
   ejb3.jar Class-Path: ejb1_client.jar 

But I think the ejb1_client.jar (client view jar file) may not necessary in app2.ear. In app2.ear->ejb3.jar, there can be a bean EJB3 that accesses app1.ear -> ejb1_client1.jar->EchoRemote:

  //In ejb3.jar
 @Stateless(name="EJB3")
  public class EJB3 {
           @EJB(lookup=java:global/app1/ejb1_client/EchoBeanRemote) 
           //look up app1.ear, ejb1_client.jar, inject ejb1 bean using its remote client view interface.
            EchoBeanRemote remoteBean;

  }

[Frits Walraven]

But I think the ejb1_client.jar (client view jar file) may not necessary in app2.ear. In app2.ear->ejb3.jar, there can be a bean EJB3 that accesses app1.ear -> ejb1_client1.jar->EchoRemote:

You will need the ejb1_client jar because of the interface definition of EchoBeanRemote. Otherwise the classes in app2.ear won't compile.

Regards,
Frits

[Himai Minh]

Thanks for Frit's reply.
That makes sense to have the EchoBeanRemote interface class in the class path to make it compile.

So, in general, even though we can look up JNDI to look up the bean or dependency injection, we still need the bean's class file in the class path to compile.

[Frits Walraven]

Yes, but we only need the remote interface of the EJB (and maybe other classes that are interface depends on), not the EJB implementation bean.