Clay Symbols aren't namespace aware - would be nice to have, wouldnt it?
Using a full HTML clay view it is possible to do things like that in a clay view: html xmlns=http://www.w3.org/1999/xhtml; xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:clay=http://shale.apache.org/clay; xmlns:s=http://shale.apache.org/core; xmlns:t=http://myfaces.apache.org/tomahawk; t:table ... /t:table /html I can use the components without using spans and the jsfid parameter. But if i use symbols to craft my page this does not work. The template does got the xmlns namespaces in the root html tag, but the symbols which gets replaced with header, footer co like this: div xmlns=http://www.w3.org/1999/xhtml; xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:clay=http://shale.apache.org/clay; xmlns:s=http://shale.apache.org/core; xmlns:t=http://myfaces.apache.org/tomahawk; jsfid=void p This is the Header. /p /div need this surrounding div workaround, to get the t:table working for example. Without the div and the namespaces, its brokenand gets not replaced by the jsf component. Should this work, is this a bug? Or is this correct behaviour? It would be nice if the symbols which gets replaced can use the namespaces declared in the root template. kind regards Torsten smime.p7s Description: S/MIME cryptographic signature
Clay Symbols aren't namespace aware - would be nice to have, wouldnt it?
Using a full HTML clay view it is possible to do things like that in a clay view: html xmlns=http://www.w3.org/1999/xhtml; xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:clay=http://shale.apache.org/clay; xmlns:s=http://shale.apache.org/core; xmlns:t=http://myfaces.apache.org/tomahawk; t:table ... /t:table /html I can use the components without using spans and the jsfid parameter. But if i use symbols to craft my page this does not work. The template does got the xmlns namespaces in the root html tag, but the symbols which gets replaced with header, footer co like this: div xmlns=http://www.w3.org/1999/xhtml; xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:clay=http://shale.apache.org/clay; xmlns:s=http://shale.apache.org/core; xmlns:t=http://myfaces.apache.org/tomahawk; jsfid=void p This is the Header. /p /div need this surrounding div workaround, to get the t:table working for example. Without the div and the namespaces, its brokenand gets not replaced by the jsf component. You could add the namespace to the table component too. You can also add an extends attribute. t:table xmlns:t=http://myfaces.apache.org/tomahawk; extends=mytable Should this work, is this a bug? Or is this correct behaviour? I tried to model it like an XML namespace but the clay markup template parser is not validating so you have a mix of html with namespaces. It would be nice if the symbols which gets replaced can use the namespaces declared in the root template. Yeah, that's not a bad idea. We would still need the namespace to be declared in the template file. Clay treats each template as a root. Once the markup is parsed, it can be included in any number of templates without re-parsing. It works more like a dynamic include versus a static include. Are you thinking about something like this? div xmlns:t=@tomahawkns ... kind regards Torsten Gary
Re: Clay Symbols aren't namespace aware - would be nice to have, wouldnt it?
Hm that makes i a little bit more clear to me. Yeah, something like the example would be nice, although because of the dynamic approach i still have to include something, which i already did at some other root template. So maybe, i'll have to include the namespaces again if i do not use the jsfid approach as the only way to craft things. Thinking about it - its maybe not so bad to have to do this more than once, makes the complete template more reusable, as the namespaces have to be there to get it working and i don't have to rely on some magic root template which maybe has them. So maybe forget it, but its really early here, i'll go sleeping and think about it a little bit later :) Torsten Am Montag, den 09.04.2007, 00:53 + schrieb Gary VanMatre: Using a full HTML clay view it is possible to do things like that in a clay view: html xmlns=http://www.w3.org/1999/xhtml; xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:clay=http://shale.apache.org/clay; xmlns:s=http://shale.apache.org/core; xmlns:t=http://myfaces.apache.org/tomahawk; t:table ... /t:table /html I can use the components without using spans and the jsfid parameter. But if i use symbols to craft my page this does not work. The template does got the xmlns namespaces in the root html tag, but the symbols which gets replaced with header, footer co like this: div xmlns=http://www.w3.org/1999/xhtml; xmlns:f=http://java.sun.com/jsf/core; xmlns:h=http://java.sun.com/jsf/html; xmlns:clay=http://shale.apache.org/clay; xmlns:s=http://shale.apache.org/core; xmlns:t=http://myfaces.apache.org/tomahawk; jsfid=void p This is the Header. /p /div need this surrounding div workaround, to get the t:table working for example. Without the div and the namespaces, its brokenand gets not replaced by the jsf component. You could add the namespace to the table component too. You can also add an extends attribute. t:table xmlns:t=http://myfaces.apache.org/tomahawk; extends=mytable Should this work, is this a bug? Or is this correct behaviour? I tried to model it like an XML namespace but the clay markup template parser is not validating so you have a mix of html with namespaces. It would be nice if the symbols which gets replaced can use the namespaces declared in the root template. Yeah, that's not a bad idea. We would still need the namespace to be declared in the template file. Clay treats each template as a root. Once the markup is parsed, it can be included in any number of templates without re-parsing. It works more like a dynamic include versus a static include. Are you thinking about something like this? div xmlns:t=@tomahawkns ... kind regards Torsten Gary smime.p7s Description: S/MIME cryptographic signature
