[jboss-user] [JBoss Tools] Document updated/added: "JbtMetawidgetSupport "

[Richard Kennard]

User development,

The document "JbtMetawidgetSupport ", was updated Mar 3, 2010
by Richard Kennard.

To view the document, visit:
http://community.jboss.org/docs/DOC-14240#cf

Document:
--------------------------------------------------------------
h1. JBoss Tools Metawidget Support
 
This page is an attempt to collect together ideas and proposals for what http://metawidget.org support may look like within JBoss Tools.
 
h2. metawidget.xml
 
Metawidget can (optionally) be configured with an external XML file, typically named metawidget.xml. For more details see http://metawidget.org/doc/reference/en/html/ch01.html#section-introduction-part1-inspector-config.
 
*XML Schemas*
 
This XML format is similar to the Seam components.xml format, in that it uses XML namespaces to both identify Java packages and allow XML schema validation. The XML schemas for all Metawidget components are automatically generated at http://metawidget.org/xsd. For example http://metawidget.org/xsd/org.metawidget.jsp.tagext.html.layout-1.0.xsd.
 
JBoss Tools could help metawidget.xml construction by being aware of all XML schemas in http://metawidget.org/xsd.
 
*ConfigReader*
 
Metawidget processes metawidget.xml using a ConfigReader class. This is lightweight, and it may be possible to run it in addition to XML schema validation to detect such errors as, say, class or package name incorrectly specified.
 
ConfigReader also does some sanity checks of its own, such as checking whether certain classes implement .equals and .hashCode, and it may to nice to alert the user of these at development time rather than application startup time.
 
h2. Annotations
 
Metawidget supports a lot of third-party annotations, but also supplies some of its own. These could be discovered and autocompleted by the UI. Details at http://metawidget.org/doc/api/index.html.
 
h2. TLDs
 
Metawidget includes TLDs for all tags, detailed here http://metawidget.org/doc/taglib/index.html

--------------------------------------------------------------