How about this? new HashSet( registry.getConfiguration( "MyConfiguration" ) );
I don't think it's worth cluttering up the API with reflection-based methods if we don't have to IMHO. -----Original Message----- From: Stefan Liebig [mailto:[EMAIL PROTECTED] Sent: Friday, July 08, 2005 10:28 AM To: [email protected] Subject: Re: Registry Vs Module: getMappedConfiguration Well, yes and no! I think it depends on the kind of "application" you are creating. If you do application development where your user interface is not an API but a GUI than definitly 'yes'. But if you are creating something like a libary with lots of people using it. They even might have paid for it, than the answer might be another. ;-) With my proposal the interface would only require 2 methods, the other would need 4 and probably more (I know: YAGNI, DTSTTCPW, ..). And yes, I knew that you would remember my thread about "unifyíng" services and configurations. :-D Stefan PS: Yes, I feel trapped. Knut Wannheden wrote: >> >>suppose that some day there will the possibilty that a configuration will be >>represented by other data structures, such as a tree or whatever. >>Wouldn´t than something like >> > > > I see where you're getting at. I've thought about that as well, but I > thought this could wait untill someone actually comes up with this > requirement and the current approach is along the lines of YAGNI and > DTSTTCPW :-) > > --knut --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
