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 -- no time to open socket, etc.
The only reason for Axis/SOAP is language neutrality IMHO. Joe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2003 1:53 AM To: [EMAIL PROTECTED] Subject: Performance comparison 2 We've implemented a test RPC style web service using the following methods: 1. EJB handler with manually created deployment descriptor. 2. WSDL2Java (thus RPC provider) with auto-generated deployment descriptor. Note that both web services implement identical operations in their implementation classes. We then did a performance comparison between the two and we discovered that the EJB handler based web service is a lot faster than the WSDL2Java generated web service. Can some please give me a reason for this disparity in performance between this two types of web services.
