----- Original Message ----- From: "Ted Husted" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> Sent: Friday, September 26, 2003 8:10 AM Subject: Re: [Chain] DTD, Design Considerations, etc. (was Re: [Chain] examples XML file available?)
> Sgarlata Matt wrote: > > I understand this difficulty which is why I was thinking that if we make it > > an explicit part of the API that you are supposed to store things in > > such-and-such place that we could be in good shape. In the example I gave, > > I was trying to say that even if different apps used the same singleton, > > they would all be isolated from each other by virtue of the fact that the > > API tells them that they need to store everything under their own unique > > attribute name, like com.mycompany.myprogram or org.apache.struts. This is > > like how Java can't guarantee two classes have the same name, but hopefully > > if people follow the guidelines they are supposed to in terms of naming > > their packages then name collisions will be less frequent. > > IMHO, the API should leave state to the underlying platform. We can > provide various examples of where you might store state for this > platform and that platform. For the most part, if Commands need to refer > to Commands, then the application can pass the Catalog up through the > Context. The API defines a place to store things, the Context, another > seems redundant. > > Whether the Context is backed by a Singleton, the Servlet Context, or > something else, can be left to the application. Well my goal with this idea was to make applications less dependent on the environment in which they run. The servlet environment can of course handle everything that this Registry can, but it is in the presentation tier. I think the Registry for the business tier should reside in the business tier. What if I want to offer a command-line interface to my application for, say, unit testing with JUnit (which I can currently do in my app for my DAOs but not for my business tier). If I use the servlet context as a registry then it is harder to write these tests. > > Yeah, you're right. I read WHITEBOARD.html and got very excited about > > Agility, and really I think this type of registry idea might find a nice > > home in Agility. Who is working on this? Is anything out there yet? I'd > > be very interested in contributing if so. > > Yes, something like Agility is a place were you might define concrete > strategies for storing catalogs within an application. Right now, I'm > still getting a feel for where Commons Chain is going to end. Frameworks > like this are best built from working examples, so we'd need to > implement Chain in a few applications before we could abstract common > functionality into a framework like Agility. Otherwise, the tail starts > wagging the dog =:) Hehe, I am often guilty of this in my own work. How do we get Chain out of the sandbox so we can start working on Agility? :) Should I move over to Struts and work on the decomposable request processor that Craig started out instead? I know one area Chain needs work is documentation, and I will be working on this in the coming weeks. > -Ted. Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
