hi guys, i'd like to inform you about some stuff I have been toying with... I told Ara and Pazu in an unrelated mail, but here you go all af you.
Exactly. Give it a dtd, and you get a Velocity template. You get beans too (a bean interface and a skeletal bean impl that gives us a head start) for each element in the dtd. We, the coders, will now code bean impls in stead of tag handlers. -and templates will *always* be ok. In fact, this stuff can be completely decoupled from xjavadoc and xdoclet. Implement the bean interfaces and let them access some other datasource than xjavadoc/xdoclet.... Since this is generic, I propose submitting a new module: xgg (xml generator generator) what do you think? Any objections? Do you want to see a zip first? >---- Original Message --- >From: "Ara Abrahamian" <[EMAIL PROTECTED]> >To: =?iso-8859-1?Q?'Aslak_Helles=F8y'?= <[EMAIL PROTECTED]> >Subject: RE: ant.blabla tags > > >> I have toyed a little with some XDoclet2/Velocity prototoping lately, >and >> I >> have come up with a very interesting concept. >> It's a DTD parser (built on JavaCC) that will generate a Velocity >template >> for the same DTD. -Using Velocity to generate Velocity! >> In addition to generating a Velocity template for the DTD it will also >> generate java bean interfaces representing >> elements in the DTD. The generated template will use these beans. > >You mean you give it the ejb2 dtd and get a velocity template?! Wow! > >> -So all we (programmers) have to do is implement these interfaces. The >> implementation of each interface is very simple, and it makes >everything >> very clean. These beans will wrap the xjavadoc API. >>=20 >> I'm ready to commit this on a separate branch so you guys can take a >look >> at >> it. What do you think? I promise you this is cooool stuff! > >Cool. > >> Aslak > >Ara. > >> > -----Original Message----- >> > From: Ara Abrahamian [mailto:[EMAIL PROTECTED]] >> > Sent: 23. september 2002 19:19 >> > To: 'Aslak Helles=F8y' >> > Subject: ant.blabla tags >> > >> > >> > Howdy pal, >> > >> > Just wanted to let you know that I'm working on autogenerating the >Maven >> > plugin. I'm almost done. I had to refactor ant.required a bit: >> > ant.required is used only for marking a parameter required ("Yes, >> > destDir is required"), while ant.not-required is used for marking it >not >> > required but with a comment ("No, Unless you set blabla parameter"). >If >> > none of these tags present then ant.not-required and "No." as the >> > comment is used. I need it because I want to know programmatically >> > whether a parameter is required or not. Unfortunately because of a >> > limitation of Jelly I probably have to introduce a new >ant.default-value >> > tag. "@ant.default-value src/java" for example. This one's used for >> > setting the default value in the plugin.jelly file. >> > >> > Ara. >> > >> > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
