Hi! I think your CreateProcess problem (error=2) means that it cant find the executable (javac.exe)... maybe there is some path error, "C:\eclipse\workspace\XMLBeans\bin\javac" looks a bit suspicious.. anyway.. good luck! /Ole
________________________________ From: Rich [mailto:[EMAIL PROTECTED] Sent: Sat 8/27/2005 10:55 PM To: [email protected] Subject: Justice XML experience (very large schema) Greetings, I wonder if anyone has tried to compile the JusticeXMl schema (jxdm) available at http://it.ojp.gov/jxdm/3.0.2/index.html. Some time ago I rolled my own "XMLBean" code on this schema (not another NIH, I just didn't know of XmlBeans:-) and was only partially successfully, so I thought I'd see how XmlBeans handles it. Jxdm is 8MB zipped and a meta-referencing nightmare. Working with the latest XmlBeans release 2.0.0. I tried to use scomp and ran into problems. ----------------------------- A heap stack overflow occurs no matter what, and I've pushed it to 2GB. The crash always occurs at the same location: supertypemetadataattributegroup.xsb, so it would not surprise me if there is a circularity issue causing XmlBeans to blow. If the schema is poor, at least XmlBeans might want to catch the problem and fail gracefully. ----------------------------- I tried to use XmlBeans on portions of the schema and ran into CreateProcess IOExceptions. I was attempting to generate class files and/or jars. I'm using sdk 1.5.0 on WinXP and probably have a java configuration error. created binary: [...] created source: [...] Time to generate code: 1.531 seconds compile command: C:\eclipse\workspace\XMLBeans\bin\javac -J-Xms2048m -J-Xmx2048m @C:\DOCUME~1\Rich\LOCALS~1\Temp\javac29358 java.io.IOException: CreateProcess: C:\eclipse\workspace\XMLBeans\bin\javac -J-X ms2048m -J-Xmx2048m @C:\DOCUME~1\Rich\LOCALS~1\Temp\javac29358 error=2 null java.io.IOException: CreateProcess: C:\eclipse\workspace\XMLBeans\bin\javac -J-X ms2048m -J-Xmx2048m @C:\DOCUME~1\Rich\LOCALS~1\Temp\javac29358 error=2 at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) at java.lang.ProcessBuilder.start(Unknown Source) at java.lang.Runtime.exec(Unknown Source) at java.lang.Runtime.exec(Unknown Source) at org.apache.xmlbeans.impl.tool.CodeGenUtil.externalCompile(CodeGenUtil .java:229) at org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.j ava:1121) at org.apache.xmlbeans.impl.tool.SchemaCompiler.main(SchemaCompiler.java :367) BUILD FAILED ----------------------------- So I abandoned the attempt to generate classes and jars and tried the -srconly option. This succeeded with one problem. All the java classes reference the generated schemaorg_apache_xmlbeans.system.s[xxx].TypeSystemHolder class. However the TypeSystemHolder only exists as a class file in the xsb directory; its java source code is not generated. I can get around this with my own IDE/jaring, but this missing source seems like an oversight. Incidentally, why is the TypeSystemHolder placed in the xsb packages rather than the src? It's the only java class located there. ---------------------------- In summary, I've been successful except for the "meta-data" schema definitions, which essentially just wrap all the other types with additional "information" attributes. I suspect XmlBeans has a small bug dealing with these, but it could also be a perverse schema definition. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
