From tomcat-user-return-47474-qmlist-jakarta-archive-tomcat-user=jakarta.apache.org@jakarta.apache.org Mon Jan 06 20:03:17 2003 Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 73875 invoked from network); 6 Jan 2003 20:03:17 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 6 Jan 2003 20:03:17 -0000 Received: (qmail 22378 invoked by uid 97); 6 Jan 2003 20:04:04 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 22308 invoked by uid 97); 6 Jan 2003 20:04:03 -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 22237 invoked by uid 98); 6 Jan 2003 20:04:02 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: "Jacob Hookom" To: "'Tomcat Users List'" Subject: RE: Tomcat 4.1.18 has problem castor?? Date: Mon, 6 Jan 2003 14:01:54 -0600 Message-ID: <000801c2b5be$75fc2df0$6564a8c0@HOOKOMJJ> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <006401c2b5bb$d3bb3b50$2368389c@tdak.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-OriginalArrivalTime: 06 Jan 2003 20:01:55.0750 (UTC) FILETIME=[76922C60:01C2B5BE] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I remember reading that one of the distributions of Castor had the same issue you are describing with parsing. My recommendation is to upgrade to Castor 4.1 and see if that fixes your issue, it did for me. Jacob -----Original Message----- From: Ali Kaplan [mailto:alikapla@cs.indiana.edu] Sent: Monday, January 06, 2003 1:43 PM To: tomcat-user@jakarta.apache.org Subject: Tomcat 4.1.18 has problem castor?? 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: -- To unsubscribe, e-mail: For additional commands, e-mail: