> > * alternate parents: in 2.0, there was a possibility to define an > alternate > parent to add child components.
isn't this transparent resolver? > > * markup fragments: in 1.3, calling renderComponent() (for Ajax requests) > fails if no markup is associated with that component or the direct parent > of > that container. In 2.0, this was no problem (I suppose because of the way > markup fragments were assigned to components) why would you call render() on something that has no markup? and then an error shouldn't be thrown? I guess in 2.0 this was an impossible situation. There was always markup attached. because that was already done in the constructor. johan
