I know internal to IONA/Progress, last year sometime we had one of our customers testing with Messages around 400MB without attachments, even larger with attachments.
Without attachments, you'll need to give the VM quite a bit of memory. We do stream, but you still need to hold the whole JAXB model for that in memory. With attachments, you can get by with MUCH lower memory usage as the large attachments would get buffered into temp files on disk. That said, I'm not sure I'd recommend that as the "best design" for most cases, but in many cases, it's unavoidable and it's good to know it works. Dan On Mon February 23 2009 5:42:45 am nicolas de loof wrote: > Hi > my current project uses CXF as WS stack to expose services. One of them > requires many inputs so the XSD becomes really huge. > > Could you please tell me what is considered to be a "large" SOAP message ? > I've found some benchmark comparison of stacks (I don't really care, I like > CXF) and other best practices about XML message weight ( > http://www.redbooks.ibm.com/redpapers/pdfs/redp4344.pdf)<http://www.redbook >s.ibm.com/redpapers/pdfs/redp4344.pdf> but > no size in bytes of a "really too big" SOAP message. > > Cheers, > Nicolas -- Daniel Kulp [email protected] http://www.dankulp.com/blog
