Hi, Most of the time it is recommended to use a dynamic model, so there is no reason to replace the component's model. Component#setDefaultModel() gives you semi-dynamic nature - you can replace the model completely with a new one. Same with #setDefaultModelObject().
What is the problem you face with it ? On Thu, Sep 27, 2012 at 9:57 AM, Michael Mosmann <mich...@mosmann.de> wrote: > Hi, > > is there any usefull application of Component.setDefaultModel(...)? IMHO > this Method is the cause for much trouble without any benefit. But maybe i > did not understand when someone should replace a component model... > > thanks > Michael -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
