Bug 3601 - Unable to compile apache/xerces/validators/schema/TraverseSchema.java using sj
Summary: Unable to compile apache/xerces/validators/schema/TraverseSchema.java using sj
Status: REOPENED
Alias: None
Product: Xerces-J
Classification: Unclassified
Component: Serialization (show other bugs)
Version: 1.4.3
Hardware: PC All
: P1 blocker
Target Milestone: ---
Assignee: Xerces-J Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-14 01:12 UTC by Dhananjay
Modified: 2005-08-25 10:17 UTC (History)
2 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dhananjay 2001-09-14 01:12:44 UTC
Hi,
   I downloaded Xerces-J-src.1.4.3.zip from http://xml.apache.org/dist/xerces-
j/ site.
   I am trying to compile this xerces. But, I dont want to use any of the 
makefiles that come with source code. I have my own make scripts, in thode I 
collect names of all the java files in the xerces hierarchy and then run sj on 
each of those. I am using sj version 3.00.042.
   I noticed a weird thing abt the compilation of 
apache/xerces/validators/schema/TraverseSchema.java file. sj just aborts if I 
try to compile this file. 
   When i took a look at this file, I found that this file is very big (9000 + 
lines) and it has nested class definitions.
   is it possible to simplify the this file, or even if it is not, then at 
least some kind of workaround.

Thanks,
Dhananjay.
Comment 1 Rahul Srivastava 2001-09-28 01:51:34 UTC
I don't think this has anything to do with Java/Xerces. Maybe some problem in
your thode script. All the source files of xerces-j compile perfectly well. Ya,
TraverseSchema is indeed a very big file but, it compiles right.

In the new design of xerces2, this file is broken into several small traverses.
Maybe your thode scriot works now with this. But, this does not seems to be a
BUG in xerces.
Comment 2 Dhananjay 2001-09-28 16:34:09 UTC
I am not using any script to compile the code. It is simple sj cpmmand that i 
am using, and I could reproduce the behaviour with different machines.
To reproduce it :
 1. Remove all the classes from the build dir.
 2. Remove the reference of xerces.jar file in the classpath, if at all it is 
present.
 3. AMek sure that you have sj 3.00.042 verison.
 4. Use the ant script with 
    build.compiler set to "Semantic" or sj class wrapper.

 Since, you have also mentioned that in the new design of xerces 2, the 
traverseschema.java file is split. Which version is that, and is that version 
product ready. Meaning, Can I use that release as a production-ready release.