> > a) there is somne redundancy here, which can trigger to some problems, > > especially when you use two deferent dtd location, one local the other > on > > the web, which might get out of sink. Is it possible to avoid it? > > b) The validation is hard coded to true and the dtd declared in the > > jboss.xml requires an http connection! What if I want to work and I am > not > > connected to the internet? JBoss went around this problem by using a > local > > resolver. Have a look at the > org.jboss.metadata.XMLFileLoader.LocalResolver > > class (if you need I can send it to you). > > yeah, we'd be better off having one resource, I'll have a look at the > JBoss code... Ara - do you have any input on this?
Well, validation is not hardcoded. You can set it true/false as you already know. But dtd location within jar file is hardcoded. It'll find the dtd locally and use it, we already use a local resolver. I don't understand what the problem is. We can make dtd location parametric, something like templateFile (say dtdFile). Is it really needed? Btw, seems like optional subtasks and jboss3 stuff need some serious tests. Big changes before a release. Bad as always. Ara. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
