On 10/27/05, Johan Compagner <[EMAIL PROTECTED]> wrote: > That NPE is already handled. > When you do a get a and somewhere in the line a null is encountered then > null is returned
Great!!! > I still am thinking of a way to create the null object then this can be > automatic if the object > i have to create has a default constructor and a setMethod is there for > that object on its parent. Wow, that's exactly what I need!!! So I don't have to create empty objects in my model anymore! > For example the parent object could implement an interface called > INullHandler with one method createObject(property) > Then the parent object is responsable for making the missing field that it > has. > But don't know about this because such an interface is wicket specific (so > ui specific) and the objects are or can be database things > Those worlds should be seperate. The interface could be optional: if the parent implements this interface, Wicket uses it, otherwise it tries the default child object constructor. -- Davide Savazzi ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
