[Registry-dev] Minor change to the Registry design

[Sanjiva Weerawarana]

+1 for this change but with a minor change: instead of isDirectory() let's 
use isCollection()? Collection seems a little bit more "implementation 
independent" to me.

BTW how would creating a directory work? Or do we still do that 
automatically?

How are we doing on hooking up the UI and the registry (in memory version 
even)? I'd like to get to the point of being able to play with it ASAP so 
that we can get the "feel" of it. Please don't worry about making a 
complete UI or any bells & whistles!

Sanjiva.

Chathura C. Ekanayake wrote:
> 
> Hi,
> 
> Currently we are having a Directory class, which has
> 
> public String[] getChildNames()
> 
> methods to get the names of child resources. We can introduce
> this method to the Registry interface with the signature
> 
> public String[] getChildPaths(String parentPath)
> 
> If we do so, we can remove the Directory class, which only contains
> the child names. Then both normal resources and directories can
> be represented using the Resource class. Then we can introduce
> 
> public boolean isDirectory()
> 
> method to the Resource class to identify whether a given resource
> represents a normal resource or a directory.
> 
> Thoughts ...
> 
> Thanks,
> Chathura
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
email: sanjiva at wso2.com; cell: +94 77 787 6880; fax: +1 509 691 2000

"Oxygenating the Web Service Platform."