--- Aslak_Helles�y <[EMAIL PROTECTED]> wrote: > Dave Neuer wrote: > > >Sorry, I suppose this is slightly off-topic WRT the > >Jakarta proposal. > > > > > Slightly, yes ;-)
Well, sorry again, but here goes some more: > >For instance, I've been bitten by differences in > the > >way XDoclet and Middlegen do variable naming (I saw > >that the original SF.net cvs checkin for > >middlegen.Util.java's decapitalize() method used > >java.beans.Introspector.decapitalize() -- what > XDoclet > >uses -- but that that was abadoned. My local > middlegen > >tree has a mod by me to go back to using > >Introspector's version. > > > > > A patch to Middlegen would be most welcome. Follow > the patching > instructions here: > http://opensource.atlassian.com/projects/xdoclet/ Umm, this may open up a whole can of worms, but... 1) What was the reason this strategy (using Introspector.decapitalize()) was abandoned in the first place (did it have something to do w/ DbNameConverter? They don't seem to have any inter-dependancies now...). 2) My local Middlegen tree is *heavily, heavily* modified by me. My employers kind of have a standing mandate that any changes I make to an OSS project that we rely on be rolled back into those projects if possible to maintain forward-compatibility as much as possible w/ future versions of those tools. However, I am not sure that some of my modifications would be interesting/acceptable to the Middlegen dev community and I'm confident that some of them would be completely unnacceptable (like completely disabling preferences). Some of my modifications might be more generally acceptable (and, this one, for instance, gets back to the origial question abot XDoclet coupling): I have deprecated the "interfacepackage" attribute for the Entity11Plugin in my local tree in favor of an attribute that I created called "substitutions", as XDoclet generically lets you do package substitutions for any of it's subtasks -- I did this because the Value Object support Eivind was working on (great job BTW!), hard-coded "interfacepackage" value as the package for the VO's it created, but In my XDoclet build I was using packageSubstitution="model" for the VO's, so compile errors would occur. Perhaps we should continue this discussion on Middlegen-devel. Dave ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
