Shankar sanjay wrote:Hi,
I've a requirement that set of Business Services(ejb) will be packaged in xyzEar file and we will build a client which will be packaged in abcEar file.
But both ear files (abcEar and xyzEar) will be deployed in same application server.
My doubt is should is use LocalView or Remote View or no-view?
I think it should be remote view because there are certain requirements for a local view sated in the specs and one of the requirements is that they should be part of same Ear file.
And even i am unclear of why is this requirement stated as such.Because if 2 ear files are going to be place in the same app server , that is same JVM , then why is this rule being implied of being in the same Ear file ??
I would like to know whether xyzEar and abcEar resides in same JVM or different JVM. (assume both the ear files deployed in the same application server.)
They will reside in the same JVM.
Note that the specs say:
Use of a session bean's local client view entails the collocation of the local client and the session. The local client of an enterprise bean must be collocated in the same container as the bean. The local client view is not location-independent
This leaves open the possibility of a Local view between Ear's, but a little bit further on:
Access to an enterprise bean through the local client view is only required to be supported for local clients packaged within the same application as the enterprise bean that provides the local client view. Compliant implementations of this specification may optionally support access to the local client view of an enterprise bean from a local client packaged in a different application. The configuration requirements for inter-application access to the local client view are vendor-specific and are outside the scope of this specification. Applications relying on inter-application access to the local client view are non-portable.
In other words: a local view between ears is possible but not required to be supported.