Clay attributes are not using xml namespaces

• Key: SHALE-170
• Type: Improvement
• Status: Resolved
• Resolution: Fixed
• Priority: Minor
• Assignee: Gary VanMatre
• Reporter: Alexandre Poitras
• Fix Version/s: 1.0.3

Environment

Operating System: All
Platform: All

Description

It is possible to define clay components by using a Tapestry-like view.
Unfortunately, the non-xhtml attributes used (jsfid, ..., ...) don't require a
namespace, wich is weird because they fall in the default namespace usually
xhtml. This lack of rigor has no consequences in our typical Internet browsers
but can cause some bugs in strict XML environments, wich are valided against DTD
or XML Schemas.

Comments

[Gary VanMatre]

We talked about adding a namespace but the limitation/consideration is with
inheritance. Clay allows you to define any jsfid. You could create your own
namespace within the jsfid if needed.

<component jsfid="xyz:outputText" extends="abc:outputText"/>

[Gary VanMatre]

I've attached the first cut of a clay xsd for xhtml templates. The schema doesn't allow creating a "top level" component definition. Only the "element" is listed. The clay parser is not a validating parser so the xsd would only be for tool support.

I'm just learning about multiple namespaces in a document but it appears that the extra namespaces have to be registered with the tool. I'm trying the Compound XML Document Toolkit (http://www.alphaworks.ibm.com/tech/cxde).

In the attempts I've made, all the nodes defined with a clay prefix are flagged in error because they don't belong within the xhtml schema. I'm not sure how facelets developers see the same thing.

[Gary VanMatre]

This is an example of how this kind of template might be used. I'd really like to hear some feedback on this. I know that Alexandre is a Facelets fan now so his input would be welcomed :-)

[Gary VanMatre]

I'm going to close this issue to indicate that it will be available in the 1.0.3 build. There is another issue open having to do with publishing the XSD, SHALE-219. I encourage others interested in html namespace support to give feedback and help plot a course.