I would prefer multiple whatever updates too, but as long as this block
approach works i guess it's an "ok" workaround.
Regarding ur solution, if that was the cause shouldn't the render fail
when i add elements using the tapestry namespace to the block and not
when i add non tapestry namespace elements like in this case ?
Like i said, it's only when i put a normal html element in the block
that it fails.
I can't add the namespace declaration to the block element anyway. I get
a syntax error. I don't think tapestry likes adding the namespace
declaration to elements that are themselves declared with the tapestry
namespace. Like <t:block>
Thiago H. de Paula Figueiredo wrote:
Em Wed, 15 Oct 2008 14:22:10 -0300, Hugo Palma
<[EMAIL PROTECTED]> escreveu:
I use the delegate to because i want the block content to be visible
when the whole page is rendered and not just after the update event.
Nice approach! But I would really like to have multiple
component/zone/block/whatever in Tapestry out of the box.
So, the page renders just fine. But, when the event is executed i get
the following error logged and nothing is updated on the UI:
[ERROR] TapestryModule.RequestExceptionHandler Processing of request
failed with uncaught exception: Namespace prefix for URI
'http://www.w3.org/1999/xhtml' <http://www.w3.org/1999/xhtml%27> is not
defined.
Try to put the XML namespace declarations in each block and zone. When
rendering just a component or block, the namespace declarations made
in the page are not available.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
