From what i remember, WebSphere generates these static proxy classes during deploy time. I don't think there will be any noticeable performance difference of generating dynamic proxies (as JBoss does) against using static proxies (as WebSphere) does. I don't have any documents which can show you the exact numbers.
thank, jaikiran, for your response...
well, we learned that we have to generate the stubs explicitly by executing create_EJBStubs.bat in WebSphere installation directory that creates us a .jar file containing stub classes for EJBs in an .ear. we deploy this .jar with our standalone client later.
the disadvantage i see is the additional effort in putting together client libraries. the advantage is, that the client do not need to download stubs again and again.
at least this is how i think it is done by JBoss...? i imagine that our users download stubs again and again, whenever they start and stop the standalone client. or even whenever the client application does a remote lookup? or even whenever it does a remote call!?
am i right? or is there something like caching on client side?
this is the reason why i am interested in this... i would like to reduce network traffic by using static ejb stubs (in single server environment)... given that there is such a feature in JBoss...?
thank you again.