Thanks, now I get it. My mistake was actually that I had misunderstood how XML / HTML is parsed into the Tapestry DOM. Now it makes a lot of sense.
Although I had already gone for the same solution Thiago mentioned (removing a child and adding a new Text child), for some reason I was convinced that all I had was a parent div Element and a child div Element with a "content", while actually the child Element had a Text child, which was the "content". I had missed that Text child so I thought my new Text was replacing the child Element, instead it was of course replacing its Text child, so it's a Text for a Text. Thanks for your patience in explaining and in spotting my reasoning mistake. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
