EJB 3 can implement 2 remote interfaces?

Yes, EJB 3 can implement two remote interfaces. How stubs are generated and in which JARs the stubs are placed is beyond the scope of the EJB specification: it is vendor specific.

Yes, EJB 3 can implement two remote interfaces. How stubs are generated and in which JARs the stubs are placed is beyond the scope of the EJB specification: it is vendor specific. I can say that the WebSphere Application Server createEJBStubs tool will generate stubs in the same JAR as the interfaces themselves.

Since the addition of dynamic proxies in the JDK and dynamic RMI-IIOP (2006), modern application servers do not require the ancient concept of manually generating stubs (let alone the even older concept of skeletons). E.g. For at least JBoss AS 4.

X+, Glassfish and partially WebSphere 7 all you need to include in your client jars are the interfaces. Nothing else is needed. (Unfortunately, for some unknown reason WebSphere only implements this relatively simple feature partially, so if you're using WebSphere and have a Java SE client, I feel your pain) Btw, also note that the proxy that you retrieve from the remote server can be directly casted to the interface.No PortableRemoteObject (another ancient concept) or anything like it is needed.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.