Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 37591 invoked from network); 6 Jan 2003 19:51:37 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 6 Jan 2003 19:51:37 -0000 Received: (qmail 1601 invoked by uid 97); 6 Jan 2003 19:52:11 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 1453 invoked by uid 97); 6 Jan 2003 19:52:09 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 12760 invoked by uid 98); 6 Jan 2003 19:41:41 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <006401c2b5bb$d3bb3b50$2368389c@tdak.com> From: "Ali Kaplan" To: Subject: Tomcat 4.1.18 has problem castor?? Date: Mon, 6 Jan 2003 14:43:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I am working on a project which uses Tomcat as servlet container and castor (ver 0.9.39) which is embedded in Jbuilder 7/8. My problem is that Unmarshaller.unmarshal(class, reader) has problem with Tomcat 4.1.18. Unmarshal method does not return proper java object, however, it does not throw any exception either. The same application is working with previous versions of Tomcat 4.1.12, etc.. Does Tomcat use any xml document parser library which may cause to conflict with castor? Does anyone have this problem before? All suggestions are welcome. Thanks, --ak -- To unsubscribe, e-mail: For additional commands, e-mail: