anonymous wrote : | 1) you have to scan through the whole message to build the outer SAAJ tree |
I don't think this is true. If we did not have SAAJ, we would still need to represent the SOAP tree with a structure like this | Envelope | Header ? | HeaderElement * | Body | BodyElement | ParamElement * | SAAJ is ok for that, it also has a sufficient API for SwA. Not using SAAJ would mean to build some API that in the end is very close to it. Also, we have no choice but to support it because it is a public user API. A user can exercise a WS communication solely by using SAAJ. I don't see a compelling reason for JBossWS not to use it internally at the level shown above. The DOM aspect of SAAJ is of course debatable, especially the deeper you go down the tree, but that's is a different story. There is no need to hold a copy of the incomming message if we can use the serializer/deserializer at the SOAPContentElement level to translate from XML to Java and vice versa. Therefore, even a large incomming message can be (eagerly) streamed to its Java object representation. On demand we can go back to XML using the associated serializer and make the DOM view available if necessary. anonymous wrote : | Is trying to optimze for a tiny memory footprint unnesessary or unrealistic? | Optimization is important, but not my major concern at this stage of the JBossWS lifecycle. We should aim for a functional implementation that passes most of the CTS by Mar 2005, ready for JBossWorld. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859232#3859232 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859232 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
