> -----Original Message----- > From: Marcus Crafter [mailto:[EMAIL PROTECTED] > Sent: Friday, July 25, 2003 11:41 AM > > Sure, I agree we should keep the interfaces lean and mean. If this > solution > is not the best, perhaps there's a better solution to the problem that we > might discover ?
I kinda like the idea of Parameterized Lookups, but as Berin pointed out, it has some issues. Here's one solution: In addition to modifying the ServiceManager contract, you'd need to either write a new set of ComponentHandlers or Lifecycle Extensions. That would be the only way to determine how to apply the runtime parameters to the service. For example, you could have a ComponentHandler which applied the parameters to the contructor. Or you could have a lifecycle extension (URIEnabled or something like that) which used the parameters to set public variables or bean fields. Of course in either of these cases, you would need to extend the ServiceManager contract. In Fortress this could be done by creating your own implementation of a ServiceManager and an AbstractContainer which provides this ServiceManager to clients. Components could then cast it your new ExtendedServiceManager to use the new lookup mechanism. This however ties your components to this implementation and creates the same problems BlockContext does. I'm not sure what all this would involve for Phoenix or Merlin. Just some thoughts. It's a very interesting question. jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
