Hi, Local Access implementation will enhance the application performance. However, calls between the Session and Entity Beans will then be limited to the local J2EE server in the same machine. I cannot foresee my application session and entity beans to be deployed locally in the same machine in the future. So what's the best solution to achieve these two? Do I write the same beans twice each for the local and remote access?
Hi, Clement I use local iterfaces in my J2EE projects and I can say that it works very faster! My session/entity beans and servlet run in same machine, under JBoss and I'm satisfied with performance. Jamal Hasanov www.j-think.com
If you forsee that the beans are unlikely to be co-located then unfortunatly you are better off relying on the slightly more bloated remote interfaces. There is no way to use the local interfaces (by definition) if the beans are not co-located and it is rarely worth the pain and effort of migrating interfaces later if you can already see that you will not be able to use the local interfaces. This is especially due to the differences in pass-by-value / pass-by-reference between the interfaces leading to many unforseen side effects when changing which one is used
The Eagle sneers at the Peacock<p>Systems Administrator<br />OrderWare Solutions Ltd<br /><a href="http://www.orderware.net" target="_blank" rel="nofollow">http://www.orderware.net</a>
Evil is afoot. But this tiny ad is just an ad:
Enterprise Java integration with Delphi and Free Pascal applications - new release 2019.02