Hi All,
Hi Marcus! Good to hear from ya :-D
Hope all is going well.
I was wondering if there was any interest out there for building some junit and Eclipse plugin's for enhancing support for testing/debugging components, etc?
you might want to look at MerlinDeveloper (or whatever they're calling it now), some eclipse plugins mainly by Andreas Oberhack to do just that in a merlin env. (LSD ducks...)
Currently, I find it a little difficult to write a junit test case for a component because it requires a container, or at least something to bring it through it's startup/shutdown lifecycle.
I'm not a big fan of custom *unit* test frameworks; its very important to test in isolation, and when you test inside a container that's no longer isolation. But that's just me :-D
So I thought about building something that would let you create a "component test case" that would let you associate a configuration, etc, amongst other things with a component. This would make it a bit easier to initialize the component in question, and then the test* methods could then operate on it.
A few versions of such a thing have been built over the years. The first one used to be called PUnit and was a "phoenix emulator". I dunno whether that lives on at loom; prolly...
I'm sure there's many other things we could do to make it easier to work with components and fortress in general inside of eclipse - any ideas?
I'm just now learning a little eclipse (I use IDEA as my IDE). There's no doubt interest in this from other users. If you want to get to work on it over here just holler and we can get you hooked up to SVN (after a vote of course ;).
cheers,
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
