Dear All,
According to the CSIRO report (http://www.cmis.csiro.au/adsat/jboss.htm), JBoss is
doing well with Stateless session beans. It implies reflection, by comparing to static
compiled codes, doesn't affect the performance much, while it has great architectural
advantages such as pluggable interceptors.
However, entity beans is not the case. One of the reason, I think, is this report uses
Option B, which JBoss doesn't support (and uses Option C instead). In other words, all
beans are trashed after a transaction is completed. It then introduces a lot of
overhead since every transaction has to reload all beans involved from database (and
you know accessing database kills the performance).
After examining the codes and a few talks with Bill, I don't think I am capable to
modify the codes to support Option B. Any volunteer is willing to do that?
Thanks and Regards,
TomN���隊X���'���u���)��Y�\�g�����������b�H zG(�� %�,�ׯzZ)��홨��x%��In�,u�ޖ�fz{e��l���q���z�m��?�X���(�� ~��zw��X�����b��?��,�ׯzZ)���
