Hm. Then again, IIRC we use strings for paths... so you probably *could* give 
these methods a "jar:xxx" string and handle that in the method. Not the 
cleanest way, but what the heck.

I'm not sure if not using the default props is that good a thing. Sometimes 
these change or get added to and you would want to get the additions.
 
Cheers, Anjo



Am 23.07.2010 um 14:56 schrieb [email protected]:

> 
>> The reason we don't do it ourself is that a lot of that stuff calls into 
>> erxfileutils and that uses path names. Fixing it would be a lot of work and 
>> make code more complicated without a lot of real gain (at least from when I 
>> last looked at it).
>> 
>> So unless any of the committers actually need to use this themselves, I 
>> wouldn't hold my breath waiting for it.
>> 
>> Cheers, Anjo
> 
> WARN  er.extensions.foundation.ERXFileUtilities  - Can't get path when run as 
> jar: ERNeutralLook - Properties
> 
> Actually, having only Properties come from and set by my program--is a 
> feature--not a bug! This "feature" has not caused me any pain--yet.
> 
> I generally would look at the properties included in the framework, but would 
> set the ones I want in my program's properties file. I am not sure what all I 
> am missing by having to work this way.
> 
> NSBundle jars have additional features that regular frameworks do not! 
> (Sometimes.) 
> -- 
>   
>   [email protected]
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/anjo%40krank.net
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to