Yep, a warning would be the perfect solution. Maybe a 'strict' mode which would be an umbrella setting for all these kinds of inconsistencies?
Quoting Aslak Hellesøy <[EMAIL PROTECTED]>: > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Hani > > Suleiman > > Sent: 28. januar 2003 12:43 > > To: [EMAIL PROTECTED] > > Subject: Re: [Xdoclet-user] DRY > > > > > > I actually like the way it's done now. The reason is that I can > > have my beans > > contain all the tags that they could require, from that I can > > further apply > > project wide generation rules from the build.xml. For example, my > > ejb might have > > view-type="both", but for whatever reason, I want to turn off > > remote views to > > check something. Right now it's a matter of removing one line in > > build.xml, > > rather than going through every bean (hundreds, in my case!) and > > changing what > > is generated. > > > > I see your point. How about XDoclet issuing a warning if it suspects > something is wrong/inconsistent? Example: > > If you specify <localinterface/> and no view-type="local|both" in any beans > you'll get a warning. > Likewise if you specify at least one view-type="local|both" and no > <localinterface/>. > > The ultimate goal here is to help people do the right thing. > > Aslak > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
