Re: serialisation problem?

[Greg Matthews]

thanks juan and mike for the responses.   F:\dev\script>java -version java version "1.3.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C) Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)     is there any way i get see the marshalling code generated by orion so i could maybe work out what's going on?   if so, can the marshalling code generated by orion be modified for debugging purposes?   thanks, greg   ----- Original Message ----- From: Juan Lorandi (Chile) To: Orion-Interest Sent: Thursday, January 18, 2001 2:32 AM Subject: RE: serialisation problem? shooting from the hip again (bad habits die hard)...   String's limit was 64K until JDK 1.3... which JDK are you using?   -----Original Message----- From: Greg Matthews [mailto:[EMAIL PROTECTED]] Sent: Mi�rcoles, 17 de Enero de 2001 1:27 To: Orion-Interest Subject: serialisation problem? dear all,   we're got a strange problem whereby a large (141K) String return value from a stateless session bean is turning up at the client as an empty string.   this happens whether we call the ejb method from a jsp or a java client external to orion.   it has also happened in other ejb methods during testing where a master-detail type record suddenly stopped being retrievable when the total size of all data in xml format as a String exceeded a certain size.   is there an upper limit on the size of variables that can be serialised?   does anyone have any ideas on why this might be happening?   thanks, greg