[forge-dev] Configuration API

[Max Rydahl Andersen]

On Dec 16, 2011, at 01:06, Paul Bakker wrote:

> Hey Lincoln,
> 
> I had a look at the Configuration API… Your branch wasn't compiling, and after fixing that I got into an endless loop in a getDelegate call, so I think you forgot to check in something. Anyway; you said to have problems saving the configuration. I added a simple test as an example of how to do that. It creates the file and loads from it correctly. 
> https://github.com/paulbakker/core/commit/8dca18c10bd52e49d671b6e8d1c01c0b9a69c917
> 
> Besides that a few remarks:
> 1) Not sure if XML is the best format, why not just use property files? They are more readable…

aren't these things better of being nested in xml than long keys in properties ?

> 4) Still not sure what to do with passwords. Encrypting would be nice, but that needs to be a two way encrypt with a private key. Where to store the private key… I don't know. Maybe we can simply store plain passwords for now and warn the user about this. How do they solve this in JBoss Tools for example? 

Eclipse provides a secure storage API which is where we store things like passwords separately.

> 
> Paul
> 
> 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

/max
http://about.me/maxandersen