You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Alex Kotchnev <ak...@gmail.com> on 2012/07/09 22:13:53 UTC
Invisible instrumentation and library namespaces
Does the "invisible instrumentation" approach work w/ library namespaces
short names inside of the t:type attribute value ? That is, if I specify a
library namespace, can I expect to use the t:type="libNs/componentName" to
work, where the libNs is the short name for "libraryNamespace" , e.g.
<div xmlns="http://www.w3.org/1999/xhtml"
xmlns:t="http://tapestry.apache.org/schema/tapestry_5_3.xsd"
xmlns:f="tapestry-library:foo">
<t:foo.Component />
<f:Component />
<div t:type="foo/Component" />
<div t:type="foo.Component />
<div t:type="f/Component />
<div t:type="f.Component />
</div>
However, the last two options don't seem to work . It's not a massive deal,
but I was just wondering if it should be working in some way that I haven't
figured out.
Cheers,
Alex K
Re: Invisible instrumentation and library namespaces
Posted by Alex Kotchnev <ak...@gmail.com>.
I'm not sure if the short library namespace is a pure XML namespace trick.
Tapestry obviously does something special to recognize the tapestry-library
prefix in the namespace declaration so that it can handle the namespace
prefixes properly.
Cheers - Alex K
On Mon, Jul 9, 2012 at 4:39 PM, Thiago H de Paula Figueiredo <
thiagohp@gmail.com> wrote:
> On Mon, 09 Jul 2012 17:13:53 -0300, Alex Kotchnev <ak...@gmail.com>
> wrote:
>
> Does the "invisible instrumentation" approach work w/ library namespaces
>> short names inside of the t:type attribute value ? That is, if I specify
>> a library namespace, can I expect to use the t:type="libNs/componentName"
>> to work, where the libNs is the short name for "libraryNamespace" , e.g.
>>
>> <div xmlns="http://www.w3.org/1999/**xhtml<http://www.w3.org/1999/xhtml>
>> "
>> xmlns:t="http://tapestry.**apache.org/schema/tapestry_5_**3.xsd<http://tapestry.apache.org/schema/tapestry_5_3.xsd>
>> "
>> xmlns:f="tapestry-library:foo"**>
>>
>> <t:foo.Component />
>> <f:Component />
>> <div t:type="foo/Component" />
>> <div t:type="foo.Component />
>> <div t:type="f/Component />
>> <div t:type="f.Component />
>> </div>
>>
>> However, the last two options don't seem to work . It's not a massive
>> deal, but I was just wondering if it should be working in some way that I
>> haven't figured out.
>>
>
> Isn't that (the short library name) a pure XML namespace trick? If yes,
> the Tapestry itself doesn't even see 'f', just 'foo', I guess.
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.org<us...@tapestry.apache.org>
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: Invisible instrumentation and library namespaces
Posted by Thiago H de Paula Figueiredo <th...@gmail.com>.
On Mon, 09 Jul 2012 17:13:53 -0300, Alex Kotchnev <ak...@gmail.com>
wrote:
> Does the "invisible instrumentation" approach work w/ library namespaces
> short names inside of the t:type attribute value ? That is, if I specify
> a library namespace, can I expect to use the
> t:type="libNs/componentName" to work, where the libNs is the short name
> for "libraryNamespace" , e.g.
>
> <div xmlns="http://www.w3.org/1999/xhtml"
> xmlns:t="http://tapestry.apache.org/schema/tapestry_5_3.xsd"
> xmlns:f="tapestry-library:foo">
>
> <t:foo.Component />
> <f:Component />
> <div t:type="foo/Component" />
> <div t:type="foo.Component />
> <div t:type="f/Component />
> <div t:type="f.Component />
> </div>
>
> However, the last two options don't seem to work . It's not a massive
> deal, but I was just wondering if it should be working in some way that
> I haven't figured out.
Isn't that (the short library name) a pure XML namespace trick? If yes,
the Tapestry itself doesn't even see 'f', just 'foo', I guess.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org