On Mon, 21 Mar 2005 09:13:45 -0500, Gili <[EMAIL PROTECTED]> wrote: > > I don't understand. So the clomeDeep() problem is gone?
No, the cloneNode(deep) has not yet been solved. > I wasn't > saying we should remove the wicket:id functionality, I was saying that > you should try testing the cloneDeep() problem against a markup that > does not contain any wicket:id tags to see if it makes a difference. > we did that already. The problem only occurs with wicket:id. <... xmlns:wicket...> seems to be fine; not the problem. But once you use wicket:id the exception is thrown. I guess what we need is either a proper DTD/schema or (what I'd prefer) use an option/feature of the xml parser (e.g. xerces) to be less strict on this issue. But a) we haven't found that property/feature yet and b) we haven't found a way to provide any feature to HttpUnit (used by jWebUnit). It is all hidden deep inside of HttpUnit (at least as far as I can tell; may be is another way of doing it, e.g. system properties or the like). Juergen ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
