Yannick Menager wrote:
I was thinking of writing a GUI tool to help assemble merlin applications, and It would have been nice if it could just go to the repository and list retrieve a list of all available components.
Unless I'm wrong, at this moment that is not possible unless i was to do some screen scrapping of the index.htmls, which would be a huge PITA ( not to mention might not work if the remote repository customised those pages ).
Spit, cough, spit, spit!
It would be then nice to have a standard listing file, with details about all the components available in the remote repository.
What do you guys think ?
DPML is a Digital Product Meta Libaray. DPML was created in order to be able to play around with exactly the sort of things your thinking of. What I would like to see is DPML functioning as the intellient gateway to the repository. Over RMI I want to get back serialized descriptions of deployment meta-data, or automated content generation over http, or redirecting request to other repositories. Getting a web app in place for dynamic content browsing should not be so hard - an server handling RMI requests will take a little more effort (infrastructure as opposed to technical overhead). Whatever - DPML should be able to deliver the services we need based on the technology we create here at Avalon.
Cheers, Steve.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
