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 [EMAIL PROTECTED] 2001-12-11 09:35 ------- Ok, this is NOT fixed, and it is now in my way of me writing a killer pair of aritcles on writing ANT tasks. When using sealed jars as libraries when writing (and using) new ANT tasks, it does become an ANT issue. JAXB is the "Java API for XML Binding", a library for generating .java files directly from a DTD and an xml descriptor file (".xjs"). Yes, it does include the crimson parser and jaxp (but internally, not as external references -- bad design IMHO, but that's what you get for "Early Access"). And yes, the jar files are sealed. What I wanted to do was to write a task that would call JAXB directly, not leaving the jvm, by calling "main()" on the compiler's class (com.sun.tools.xjc.Main), but because the jar files are sealed, i get an access violation just because the files are in the lib directory of ANT. ANT won't even start up when they're in the CLASSPATH in any way. Obviously, the workaround is to extract the contents of the jar, remove the manifest, and make an unsealed jar whose sole purpose is to be the version placed inside Ant's lib directory (and while you're at it, remove the redundant xml parser). But I'm not entirely sure that's legal according to Sun's license (I'd have to re-read it), and in any respect, its not something I'd like to be forced to recommend to my readers. As more development tools come about that Ant users want to embed, the issue of dealing with this sealed jar thing does need to be resolved, one way or another. Yes, it is Sun's fault for, as the comment describes, including all its dependencies in the jar itself, but its something that's going to happen regardless, and if there's a way around it, Ant should find it. Joe -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
