> > >Well, about the "Don't know what to write here;" the answer is you can't > > >because javdoc's doclet api doesn't have a method to retrieve that. > > >Hopefully xdoclet's xjavadoc api will let you do that. But for the time > > >being, you can follow Dmitri's proposal (@ejb:interface-constant > > >view-type="local" declaration="String FOO = \"bar\""), though it's ugly > > >imho. > > > > That _is_ ugly. I hope xjavadoc will save the day here too. Until then I do > > some hack. > >what's ugly about it? As I understand it, Ara's criticism is over the >placement of constants in an interface. atm, we have >finders: > > @ejb:finder query="java.util.Collection findAll()"
Ah, what I thought ugly was placing something that's pure Java into a comment and into the xdoclet description of the bean. You have to quote citation marks and you don't get the highlighting of code the editor normally gives you. I would say that the same thing goes for finder in a way. > What I think is ugly is having the same field declaration in >the bean class as in the interface. Alternatively, Ara's suggestion of >using a constants class is obviously also a perfectly valid >way of doing things. Since the field is final static is not like a variable as such but as a name for something. Therefore I don't think it's too ugly to have the same constant in several places since they have a common root and can't be out of sync. I see it more like #defines in a header file in C/C++ that are included in several .c-files. I like that better than having to refer to a file (the interface) that haven't been generated yet. Since the interfaces are generated from the bean class, I would like to keep dependencies the other way, from the bean class on the interfaces, at a minimum. I can imagine someone in the future reading the code and pulling their hair when they cannot find that class the code refer to all the time. I've already lost some of that by having setData/getData methods but if I could leave it at that it would be nice. Not that it's of religious importance. If it's done in another way I'll use that. I just don't have to think that it's the best way? ;-) /Daniel - cold and wet. _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
