ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 5302] - Sealing Violation
Date Wed, 12 Dec 2001 17:08:43 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5302>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5302

Sealing Violation





------- Additional Comments From acroyear@io.com  2001-12-12 09:08 -------
I can't tell the readers to remove Ant's java parsers (and i'm not the one who
had JAXB in ext/ -- i was just trying to put it into ANT_HOME/lib).  The concern
is that the parser provided with JAXB may be old, as in the pre-crimson,
pre-jaxp, xml parser that sun was releasing back in "the good old days".  I got
the impression from looking at the files listed in the jars that its not even
SAX2 or DOM2 compliant, which may cause significant problems if Ant uses either
of those libraries.

My solution basically is to not create a "task" for calling jaxb, but continue
to use a Java task, with fork="true" and includeAntRuntime="false", and the JAXB
files in the classpath for that process only (well, and for the javac and any
testing target).  I already had that working, and it was already more portable
than using apply and calling the wsc script (which was solaris only).

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message