> My guess is that you have a stacktrace on the server side that will
> point to the problem. If its still not clear what the cause is, post
> your code and the stacktrace and maybe we can help.
I understand, but this is the only output what I get (on server (in fact:
service) side). Code that makes an output is in try/catch and there is no
exception thrown. My code doesn't throws any exceptions. My service method
finished normally, and this is what I get in Tomcat's (5.5.17) console AFTER my
"return response; // OMElement response;"
There is one thing in addition. When I cut down the output, so the output SOAP
message is smaller (no changes in service code!), then everything works fine.
So It's something like, that I'm trying send too big SOAP messages. Is some
restrictions in SOAP standards/Axis2 engine about SOAP message max size?
I think sourcecode isn't needed. Imagine sth like this (hand coding now):
OMElement response = factory.createElement( ... );
for( int i = 0 ; i < 1000 ; i++ ) {
response.addChild( factory.createElement( ... ) );
}
return response;
(I will try to do it tomorrow in work, but I'm sure that It will generate the
same error.)
Thanx for answer.
Radek Adamiak
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
