1. EJB uses RMI over IIOP instead of HTTP as its transport layer. Far fewer
bytes involved in sending complex objects.
2. EJB uses native Java serialization rather than serializing to XML. Far
fewer bytes and internal serializer implementations can be faster.
3. EJB uses persistent connections --
Can you provide more details on this (maybe source)? Did you modify the
WSDL2Java generated skeleton to call the EJB, etc?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, August 04, 2003 1:53 AM
To: [EMAIL PROTECTED]
Subject: Performance comparison 2
We
Maybe the WSDL2Java-generated code uses a lot of reflection?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: 04 August 2003 06:53
To: [EMAIL PROTECTED]
Subject: Performance comparison 2
We've implemented a test RPC style web service using the following methods
