I wanted it removed because it looked like there was a resource named
"root" or "top" or whatever.
Ok - I figured there would be a way of colour-coding or otherwise
visually showing that the resource isn't called "root".
15. I'm very scared by the ability to change the config via the Web
UI. It seems like one click of a button and maybe I've switched to
inmemory and then I lose a bunch of data.
Yes. But we will switch default to be HSQLDB file based one instead of
in-memory.
That's not answering the question Deepal .. I think the concern is that
if you change the underlying DB by mistake you're, um, screwed.
I guess you really aren't - if you switch and switch back effectively
you've just "connected" to an existing registry datastore. So in effect
the UI is somewhat de-coupled from the underlying datastore.
I still don't understand the usecase for this. I hate having "cool"
features that don't have a use-case. And this seems like one of them.
This is what I expect to be in a config file and I don't expect to
change it often.
The other points raised by Paul and Glen need to be looked into too.
Given the closeness to the 0.1 release timeframe, I think we may have to
leave a bunch of those as known issues for the next iteration.
Can we try and fix all the small stuff quickly and then I will raise
JIRAs for anything we don't get fixed straight away.
Paul
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
Office: +1 646 290 8050
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
