Sergei Batiuk wrote:
I would like to discuss this before posting to the Geronimo WishList.
=== Stubless and stubs-enabled deployment ===
One of the greatest problems in the EJB development, is that EJB deployment usually takes a lot of time (in servers like Weblogic, or SunONE appserver), because a container needs to generate and compile stub classes for EJBs. JBoss and JRun provide fast deployment because they use reflection instead of code generation and compilation. However, the EJB invocation based on reflection is known for being slower than the one based on stubs.
Therefore, two types of EJB deployment required:
1. For development, it's best to use stubless deployment, based on reflection (like in JBoss and JRun). This will enable fast deployment cycles. Performance impact on remote method invocation is not critical during application development; but the speed of deployment is.
Hi Sergei,
That's exactly how OpenEJB works so users don't have to wait till the stubs are generated, but merely copy the file into the beans directory. Proxy does it all and allows OpenEJB to choose between local or remote mode depending on configuration.
2. For production, it's best to use deployment based on stubs to provide better performance (like in Weblogic and SunONE). After you make sure your EJBs work well, you won't need to deploy them often. In production remote method inocation performance matters, and the speed of deployment is not that important.
OpenEJB team has several times told over to incorporate generating stubs while deploying beans, but somehow it lost our attention. I guess our dream about the two types of deploying beans will finally come true in Geronimo.
As to the idea I like it much. I think it needs some tests to see if it would really improve things.
Am I the only one who can't manage the amount of emails in the mailing list? I decided to move OpenEJB test machinery to Geronimo (esp. starting the server before tests are performed) some time ago, but I'm lost :-(
Sincerely,
Sergei Batiuk.
-Jacek
