I just committed an example where this would be useful: org.apache.avalon.excalibur.i18n.test.DefaultBundleMatcherTestCase and the corresponding .xtest file. The issue here is that usually the lifecycle of BundleMatcher inplementations would be managed by BundleSelector. However, in the test, I don't want to go through BundleSelector, I want to bypass that and test only BundleMatcher implementation, not BundleSelector.
So, AFAISee, my testcase needs to manage the lifecycle and for that I need some configuration data... If this issue could be solved otherwise, I'm all ears. :-) On a similar note, I saw some object factory implementations in excalibur. Are there any benefits in favor of using those instead of doing directly classForName() in my code (as I'm doing right now in some places)? Would they manage the lifecycle for me? What will happen if I lookup a component through manager, would save it somewhere and would look up another one. It would return the same instance, as there is only one instance per component in manager, correct? Willing to learn better ways of doing things, Neeme PS It would work for everybody. > -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 31, 2001 8:54 PM > To: Avalon Developers List > Subject: Re: getting configuration from ExcaliburTestCase > > > Neeme Praks wrote: > > > > :-) > > I understand that the ComponentManager is configured automagically and I > > don't want to configure that manually. > > I just want to pass some configuration data into the TestCase itself. > > What kind of configuration data? I want to come up with something that > works for everybody... > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
