On Wednesday 19 November 2003 04:23, [EMAIL PROTECTED] wrote: > > Since there is a Repository spec going on, I thought that I should create > > the RepositoryAgent & RepositoryAgentFactory for this implementation, as > > a show case. > > Is there Directory/Container support in the spec? > > I don't think I really understand. Are you asking if this repository API > supports containers? If so its just an API and you can use if for > anything.
LOL, an API I can use for anything? Making coffee? I had a long conversation with Stephen yesterday. Long because there was some complete short-circuit in communications, I didn't understand the current concept, and he didn't see my angle, possibly because I used the wrong wording. Finally, it came clear though; The API has a "Dependency View" and you need a "leaf object" from which you can traverse the dependency graph. My angleis that I need a "Categorized View", where you have a "root object" and can traverse (browse) a categorization tree. I think, the conclusion I made was that except for "domain" there is no concept of categorization. But I could be wrong. What I am aming at is that the repository can be "Navigated" from a root container. See attachment (also available at http://niclas.hedhman.org/repository/rep-browser1.jpg ). > > What is the thread and event model? > No thread model and no event model. Basically it's an API where you do the > following to use it. BTW its based on the provider pattern: Ok. > InitialRepositoryFactory l_factory = new InitialRepositoryFactory() ; > FactoryContext l_context = l_factory.getDefaultContext() ; > l_context.setCacheDir( "/opt/projects/repository" ) ; > Repository l_repository = l_factory.create( l_context ) ; Thanks for a template. > Note that the InitialRepositoryFactory could have taken a Jar > ArtifactDescriptor as a constructor argument. The descriptor is used as an > alternative repository implementation to use instead of the defualt > implementaion which the code above uses. This Repository object produced > in the end should be equivalent to your RepositoryAgent as I remember from > our previous conversations. Slightly different, due to the View aspect I tried to point out above. I am also a bit "nervous" whether inter-repository dependencies are supported, since that requires many Repository instances, and stronger Identification of services and implementations. I'll probably get to this later... Well, I see what we can do... But not right now. Niclas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
