当前位置: 技术问答>java相关
Servlet/JSP可以使用Local Interface么?
来源: 互联网 发布时间:2015-11-03
本文导语: Can or how a servlet/JSP call an EJB using local interfaces or directly to the bean class? I think it is impossible because servlets/JSPs are in web container while EJBs are in EJB container. They are in different JVMs. Someone said weblogic6.1 u...
Can or how a servlet/JSP call an EJB using
local interfaces or directly to the bean class?
I think it is impossible
because servlets/JSPs are in web container
while EJBs are in EJB container. They are in
different JVMs. Someone said weblogic6.1 uses classload to do the
work, but what about the transaction?
Please advise. Thanks.
local interfaces or directly to the bean class?
I think it is impossible
because servlets/JSPs are in web container
while EJBs are in EJB container. They are in
different JVMs. Someone said weblogic6.1 uses classload to do the
work, but what about the transaction?
Please advise. Thanks.
|
Hmmm.......somebody said there are no containers in Weblogic Servers, logically and conceptually.
But in my opion, WebLogic does indeed have separate Web and EJB Containers. This allows BEA to license the Containers individually. Nothing in the J2EE specification even comes close to hinting that the Containers must run in separate JVMs. In fact, it does just the opposite with the idea of a EAR (Enterprise Application Resource). To comply with the specification an EAR must have the Web and EJB components residing in the same JVM to allow for Local calls between components.
That's all.
But in my opion, WebLogic does indeed have separate Web and EJB Containers. This allows BEA to license the Containers individually. Nothing in the J2EE specification even comes close to hinting that the Containers must run in separate JVMs. In fact, it does just the opposite with the idea of a EAR (Enterprise Application Resource). To comply with the specification an EAR must have the Web and EJB components residing in the same JVM to allow for Local calls between components.
That's all.