Do it in bean’s @PostConstruct method. @ManagedBean @RequestScoped public class Bean { private List<Item> items; @EJB private ItemService itemService; @PostConstruct public void init() { items = itemService.list(); } public List<Item> getItems() { return items; } } And let the value reference the property (not method!). <h:dataTable value=”#{bean.items}” var=”item”> In the @PostConstruct you have the advantage … Read more
EL (Expression Language, those #{} things) won’t cache the result of the calls or so. It just accesses the data straight in the bean. This does normally not harm if the getter just returns the data. The setter call is done by @ManagedProperty. It basically does the following: selector.setProfilePage(request.getParameter(“profilePage”)); The getter calls are all done … Read more
If you want to validate when the property is set, you need to use non-auto properties (i.e., manually defined get and set methods). But another way to validate is to have the validation logic separate from the domain object. class Customer { public string FirstName { get; set; } public string LastName { get; set; … Read more
Three solutions: Implement your object as a Proxy, which is designed to do exactly what you want. Yet, it is only a draft and currently only supported in Firefox’ Javascript 1.8.5 It was standardised with ES6, but might not yet be available in all environments. Always fill your translation object with a complete set of … Read more
The getter of the class sits on the .prototype object, not on this, that’s why your attempt to delete it fails (and, as Jeremy points out, it is not deletable). You can however simply create an own property on the instance that shadows the getter: class a { get b() { Object.defineProperty(this, “b”, { value: … Read more
Use just the .getter decorator of the original property: class superhuman(human): @human.name.getter def name(self): return ‘super ‘ + self._name Note that you have to use the full name to reach the original property descriptor on the parent class. Demonstration: >>> class superhuman(human): … @human.name.getter … def name(self): … return ‘super ‘ + self._name … >>> … Read more
Looking through the nowjs source code, I believe they do this by continuously monitoring the now object and pushing changes between client and server whenever they are detected. I admit I haven’t fully grokked their code yet, however. In a browser, this would be done with some fun setInterval hacks. EDIT: yes, that is indeed … Read more
I don’t have a problem with Holub telling you that you should generally avoid altering the state of an object but instead resort to integrated methods (execution of behaviors) to achieve this end. As Corletk points out, there is wisdom in thinking long and hard about the highest level of abstraction and not just programming … Read more
I have personally settled on using an underscore prefix for ivars, and this kind of synthesize @synthesize name = _name; That way I don’t mix them up. The major issue with not using self is that this code _name = … is very different from self.name = … When the @property uses the retain option. … Read more
Set and Get methods are a pattern of data encapsulation. Instead of accessing class member variables directly, you define get methods to access these variables, and set methods to modify them. By encapsulating them in this manner, you have control over the public interface, should you need to change the inner workings of the class … Read more