Hi guys, and thanks for the answer.
First of all was a mistake in my message-style web services, so for very small messages (an xml request with one item) as I expected the message style looks to be faster then RPC style(3-5 times). Unfortunatly I had to send a large amount of data over Web services(one of my test request is an 6 MB xml file - 5000 items) and it looks like the performance is signifian diminshed in this scenario(I hope I will have some benchmarks later today-in USA now is morning). In this case also, Tomcat crashes very often, and uses a large amount of memory - issues that makes a messages style web services unusable for this scenario. It looks like working with huge DOM objects is very,very expensive(which actually is not a big surprise) and not practical. Also tomcat prove it to be completely unstable in such situation(fortunatly in production I can use another web container) When I will have my complete benchmarks, I will send to you. Anyway, Is still have some question, for you guys, if you can help me: - What will be the advantage of using Document styly instead of RPC(I can't figure out, which is the main difference between those two as long as both of them are using Axis' serialization/deserialization mechanism) - What will be the best way from your experience to send big xml file with axis(let's say up to 10MB), without using attachments, and considering that the clients of my web services, are at least .NET application and Java application(but also is possible to have some python clients) - so I need interoperability with other web services implmentations - Is it any possibility to access the xml messagesas(buy changing the axis servlet, writing some handlers, writing some filters or anythign else) as a stream and parse with SAX, or to get an xml document model more efficient like JDOM or something like XmlCursor from XMLBeans project ? Romulus -----Original Message----- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Friday, May 28, 2004 6:31 AM To: [EMAIL PROTECTED] Subject: RE: Is it message style MUCH slower then rpc? The MSG provider (WSDD style of MESSAGE) uses DOM and the RPC provider (WSDD styles of RPC, WRAPPED, or DOCUMENT) uses SAX. The MESSAGE provider transforms requests into a DOM. The RPC provider uses the serialization framework to transform requests into Java objects. This accounts for the very significant difference in performance that you see. Keep in mind, though, that the RPC provider supports both RPC/Encoded and Document/Literal messages. In order to make a fair comparison of RPC/Encoded and Document/Literal performance, you should compare WSDD style RPC with WSDD style WRAPPED or DOCUMENT. Here you should see very little difference in performance. Anne -----Original Message----- From: Nelson Minar [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 8:44 PM To: [EMAIL PROTECTED] Subject: Re: Is it message style MUCH slower then rpc? >It looks like the message style web service is 6 -20 times slower >then the old version using JAXP-RPC model. I can't answer your questions, but I'd be very interested to know more. What kind of data are you passing back and forth? It should be straightforward to make a performance test that was the exact same service as document/literal and rpc/encoded and compare how fast they run. >Is it really the message style very slow comparing with rpc style? I don't see why it should be. >Is true that in rpc style an SAX parser is using for parsing the SOAP >message, and with message style we need DOM, but is this issue the source >for such a huge loose in performance? I don't know, but would like to know the answer myself. >Do I have to make some settings in web container or web app to get better >performance with message style? You want to make sure sendXsiTypes and sendMultiRefs are both turned off in the configuration of Axis. But come to think of it, those parameters may not be relevant to document/literal.
