BTW - will we be seeing you at this years GetTogether in Gent?
hehehe: http://jroller.com/trackback/lsd/Weblog/lsd_gettogether_nope
I guess I'm not really looking to do too much, perhaps create an abstract test case class that has an associated xconf fragment, that defines how the component should be instantiated/created by the container, and the rest would be normal junit processing.
don't we have something like that already? I'm sure I saw it somewhere sometime...
I think most of us have custom solutions in our workareas to do this already
prolly. Another thing I seem to recall is Pete has some of this hammered out for DNA (jcontainer.org).
Cool, well I think I better have something written up first :)
hehehe. You were an avalon committer and you worked on this before, so I consider you "emeritus". Dunno what others think :-D
I was thinking of some of the following:
* Wizards for creating component interfaces and implementations (including auto generation of the @qdox tags for metadata).
IDEA has "templates" and "live templates". I had a whole bunch of those set up at some point for stuff like this. Must be around somewhere...I could go hunt the archives if someone is interested...
* The JUnit style help described above
* Something like 'Open Call Hierarchy', but slightly different in that it displays references where the given component was 'looked up'.
no idea what that is...
* Something that extends the compiler to generate the metadata/services.list, etc, so that running/debugging in eclipse works out of the box.
couldn't we just write a no-external-files-needed version of fortress so that running/debugging works out of any box? Must be possible.
I'm sure there are others?
I dunno; not so big on UI stuff. Eclipse/GTK seems real slow (on linux that is). I doubt I want to use it :-D
-LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
