sorry... <jbossxml validatexml="false" />
trying to function when I should be in bed... not a good idea (o: cheesr dim On Sun, 4 Nov 2001, David Budworth wrote: > In the JBossXML task? > > I can't find where that goes in the docs. Or do you mean go edit the source? > > If it goes in the build.xml file, I have no idea where (I added > setValidate="false" as an attribute to the <jboss/> tag, but that seemed to > fail) > > hychmdp (HopeYouCanHelpMyDeadProject), > > -David > > > On Sunday 04 November 2001 17:24, Dmitri Colebatch wrote: > > You can use setValidate="false" in the jbossxml task. I cant see any > > reason why this shouldn't work. > > > > hth > > dim > > > > On Sun, 4 Nov 2001, David Budworth wrote: > > > Ok, now that that you've made xdoclet stop the build, how can I turn this > > > off? > > > > > > I'm using xdoclet to generate beans for JBoss 3. And since there's no > > > JBoss 3 DTD, the jboss.xml validation step fails, thus killing the build. > > > > > > I either need XDoclet not to kill ant's build, or have some way to make > > > ant ignore the javadoc failure and keep going. I would assume that > > > making targets ignore on failure could work. But I can't find it in the > > > Ant docs > > > > > > I tried editing jboss_xml.j, to remove the DOCTYPE tag, but it still > > > fails to validate (and I checked, jboss.xml has no doctype when > > > generated), and XDoclet stops the build. > > > > > > I was always getting the error before, but since Ant didn't care about > > > the failure, it all went fine. > > > > > > -David > > > > > > On Sunday 04 November 2001 12:26, Ara Abrahamian wrote: > > > > Update of /cvsroot/xdoclet/xdoclet/core/src/xdoclet/tags > > > > In directory usw-pr-cvs1:/tmp/cvs-serv6729/core/src/xdoclet/tags > > > > > > > > Modified Files: > > > > AbstractProgramElementTagsHandler.java ClassTagsHandler.java > > > > IdTagsHandler.java MethodTagsHandler.java > > > > PackageTagsHandler.java ParameterTagsHandler.java > > > > Log Message: > > > > lot of things: > > > > - ejbName()/commName()/jndiName()/localJndiName everywhere, it uses > > > > ejbName if ejb:bean name param is missing - IfIsAConcreteEJBean > > > > enhanced, I also changed PersonBean to show that you don't have to put > > > > any ejb:bean generate="false" to set it an abstract bean - now ant > > > > stops if an error occurs (It's just a dirty workaround till we submit a > > > > fix to Ant) :o) - New high level methods > > > > getClassTagValue/getMethodTagValue use it everywhere instead of > > > > getParameterValue/getText combination. - getTagValue enhanced: now you > > > > have a better @tag inheritance mechnism, so if you specify ejb:bean > > > > aa="gg" in Base and also specify ejb:bean bb="ff" in child it doesn't > > > > stop searching the hierarchy at child (previously it stoped when the > > > > first class in hierarchy had the @tag). - and things that I don't > > > > remember ;-) > > > > > > > > _______________________________________________ > > > > Xdoclet-devel mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > > > > _______________________________________________ > > > Xdoclet-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > > _______________________________________________ > > Xdoclet-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
