A wise old hermit known only as Vincent Harcq <[EMAIL PROTECTED]> once said:
> I think a lot of user are using the xml validation. Personnally I > don't. > We should add it to samples build if it goes OK now to be sure > developers don't by pass it. It already does have for some of the subtasks (standard DD, weblogic, jrun) - that's how I spotted it. > Also if a lot of users use that and it does not work, is it a good > moment to create version 1.1.2 ? > > Vincent Which was why I wanted to know if it was broken for anyone else - I've got the DAO changes ready to check in and Bluestone 99% there, but wasn't going to check them in if they broke the samples, given that next on my list was to build the new version... Andrew. > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On Behalf > > Of Andrew Stevens > > Sent: dimanche 3 mars 2002 0:29 > > To: [EMAIL PROTECTED] > > Subject: Re: [Xdoclet-devel] Samples won't build? > > > > > > The exception's being thrown during XML validation; it's not just the > > deploymentdescriptor subtask that's affected - if I set > > validatexml to > > false on that one it just fails on the weblogic subtask > > instead. If I set > > it to false on weblogic, it fails at the jrun task instead... > > > > The ejb-jar.xml file *is* valid, though - it's validated okay > > by Netbeans' > > XML module (at least, once I change the DTD's system ID to > > point to the > > local disk copy). So, it appears to be a problem with XDoclet's > > validator. > > > > I don't suppose the java.io.File->java.net.URL changes could > > have messed > > up the validation? (e.g. by stopping it resolving the DTD) The only > > change to xdoclet.util.XmlValidator since my i18n stuff (and > > I know it > > worked okay after that) is "Refactored the use of > > java.io.File for reading > > to use java.net.URL instead. This is cleaner and safer, and makes it > > possible to read templates from within other jar files" What > > about the > > subsequent change to fix the file:/// problem for > > templatefile? Would > > that need anything equivalent doing in the XmlValidator too? > > > > Again, am I the only one that's getting this? > > > > > > Andrew. > > > > > > A wise old hermit known only as Andrew Stevens > > <[EMAIL PROTECTED]> once said: > > > > > Is it just me, or is something wrong with building the > > samples? I do > > > a > > > total-clean, build the main dist, go the the samples and > > build, and I > > > get > > > > > > [ejbdoclet] javax.xml.parsers.FactoryConfigurationError: > > > java.lang.ClassNotFoundException: > > > org.apache.xerces.jaxp.SAXParserFactoryImpl > > > [ejbdoclet] at > > > > > javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactor > > y.java:150 > > > ) > > > [ejbdoclet] at > > > xdoclet.util.XmlValidator.validate(XmlValidator.java:169) > > > [ejbdoclet] at > > xdoclet.XmlSubTask.engineFinished(XmlSubTask.java:132) > > > [ejbdoclet] at > > > xdoclet.TemplateSubTask.startEngine(TemplateSubTask.java:550) > > > [ejbdoclet] at > > > xdoclet.TemplateSubTask.startProcess(TemplateSubTask.java:354) > > > > > > > > > Andrew. _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
