The question was: do we introduce one XML namespace for Tapestry
components and a second one for the (finite set) of Tapestry
directives? I chose to have a single namespace. This could be changed
in the future to have a distinct XML namespace for components and a
separate one for directives. The X
On Fri, Aug 14, 2009 at 11:05 AM, Thiago H. de Paula
Figueiredo wrote:
> Em Fri, 14 Aug 2009 11:57:09 -0300, Michael Gentry
> escreveu:
> Take a look at http://tapestry.apache.org/tapestry5.1/guide/templates.html,
> section "Tapestry Elements".
I had seen that section before, but it wasn't really
Em Fri, 14 Aug 2009 11:57:09 -0300, Michael Gentry
escreveu:
I'm assuming t:body isn't really a component, but a different form of
magic.
is not a component.
Are there other "components" that aren't really components
Take a look at
http://tapestry.apache.org/tapestry5.1/guide/templat
Hi all, I know I'm still learning, but I'm a bit puzzled as to why:
works just fine, but:
and
both error out with:
org.apache.tapestry5.ioc.internal.util.TapestryException
Unable to resolve 'body' to a component class name. Available
component types: ActionLink, AddR
