Still not 100% sure of what you want, but this quick bit of code (untested) might get you on the right track (or at least help clarify what you want). void ReportValue(String propName, Object propValue); void ReadList<T>(List<T> list) { var props = typeof(T).GetProperties(); foreach(T item in list) { foreach(var prop in props) { ReportValue(prop.Name, prop.GetValue(item)); … Read more
self.object = nil calls your setter, which will release the old value, set the member to nil, and possibly do other things (it’s a method, so it could do anything). The “anything” part of that is potentially dangerous; see this question, for example. [object release] releases the old value, but leaves the member as a … Read more
A hot debate about the subject can be found here: Width attribute for image tag versus CSS To sum it up: The gain from declaring a width value and an height value (which may not be the original physical dimensions of the image) or from css declarations (like width: [valueX]; height: [valueY];) is that it … Read more
One word: inheritance. Properties are inheritable while fields are not. You can use fields in an inherited class, but not alter their behavior by making them virtual. Like so: public class Foo { public virtual int MyField = 1; // Nope, this can’t public virtual int Bar {get; set; } } public class MyDerive : … Read more
Unless you have directly defined the backgroundColor on the element itself, you have to use getComputedStyle() or currentStyle to get the value of a style property. A method that is compatible with multiple browsers would look like this: function getStyle(el,styleProp) { if (el.currentStyle) return el.currentStyle[styleProp]; return document.defaultView.getComputedStyle(el,null)[styleProp]; } You can see a working example on … Read more
I ran into the same problem some time ago and found a document on the Apple Developer Connection recommending to provide your own implementation of the setter. Code sample form the linked document: @interface MyClass : NSObject { NSMutableArray *myArray; } @property (nonatomic, copy) NSMutableArray *myArray; @end @implementation MyClass @synthesize myArray; – (void)setMyArray:(NSMutableArray *)newArray { … Read more
You can just get the property by name: Foo f = new Foo(); f.Bar = “Jon Skeet is god.”; var barProperty = f.GetType().GetProperty(“Bar”); string s = barProperty.GetValue(f,null) as string; Regarding the follow up question: Indexers will always be named Item and have arguments on the getter. So Foo f = new Foo(); f.Bar = “Jon … Read more
No you can’t. PropertyPlaceholderConfigurer is a BeanFactoryPostProcessor, it is only “alive” during bean creation. When it encounters a ${property} notation, it tries to resolve that against its internal properties, but it does not make these properties available to the container. That said: similar questions have appeared again and again, the proposed solution is usually to … Read more
The Expression API supports this in .NET 4.0, but sadly the C# compiler doesn’t add any extra candy to support. But the good news is that you can trivially take a “get” expression (which the C# compiler can write) and re-write it as a “set” expression. And even better; if you don’t have .NET 4.0, … Read more
You need to annotate your TestConfiguration class with @EnableConfigurationProperties as follows: @EnableConfigurationProperties public class TestConfiguration { @Bean @ConfigurationProperties(prefix = “test”) public TestSettings settings (){ return new TestSettings(); } } Also you only need to include TestConfiguration.class in @ContextConfiguration of your SettingsTest class: @TestPropertySource(locations = “/SettingsTest.properties”) @RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(classes = TestConfiguration.class) public class SettingsTest { …