From adffaces-commits-return-408-apmail-incubator-adffaces-commits-archive=incubator.apache.org@incubator.apache.org Thu Jul 27 22:41:19 2006
Return-Path:
- Tag name: <af:attribute>
+ Tag name: <tr:attribute>
@@ -37,19 +37,19 @@
Example:
+ <tr:table var="emp" value="#{employees}">
+ <tr:attribute name="banding" value="none"/>
+ <tr:column >
+ <tr:outputText value="#{emp.ename}">
+ <tr:attribute name="styleClass" value="#{emp.role}"/>
+ </tr:outputText>
+ </tr:column >
+ <tr:column >
+ <tr:commandButton action="#{emp.viewDetails}">
+ <tr:attribute name="label" value="More on this #{emp.title}"/>
+ </tr:commandButton>
+ </tr:column >
+ </tr:table>
- Tag name: <af:forEach>
+ Tag name: <tr:forEach>
The forEach tag is a replacement for the JSTL @@ -35,32 +35,32 @@
- Tag name: <af:region>
+ Tag name: <tr:region>
- UIComponent class: org.apache.myfaces.adf.component.UIXRegion
+ UIComponent class: org.apache.myfaces.trinidad.component.UIXRegion
- Component type: org.apache.myfaces.adf.Region
+ Component type: org.apache.myfaces.trinidad.Region
This component inserts a region (defined by a separate page
- that starts with <af:regionDef>)
+ that starts with <tr:regionDef>)
into the current page. The "id" attribute is required on this
component, which implements NamingContainer. A region may have
a value, custom attributes, or both. The value will be
made available to the region definition using the "binding"
EL attribute. Custom attributes, defined with
- <f:attribute> or <af:attribute>, will also
+ <f:attribute> or <tr:attribute>, will also
be made available to the region definition - see the
- <af:regionDef> tag documentation for more information.
+ <tr:regionDef> tag documentation for more information.
- Tag name: <af:regionDef>
+ Tag name: <tr:regionDef>
- This tag, in conjunction with af:region, allows
+ This tag, in conjunction with tr:region, allows
a common UI (a region) to be defined. Once
defined, the region must be registered in "WEB-INF/region-metadata.xml".
- A registered region is referenced with the <af:region> tag.
+ A registered region is referenced with the <tr:region> tag.
A region can be used
many times, either on the same page, or on multiple pages.
A single region must be defined in its own page, and
- the <af:regionDef> must be the top level tag on that page (it
- replaces <f:subview>). See the <af:region> tag to see
+ the <tr:regionDef> must be the top level tag on that page (it
+ replaces <f:subview>). See the <tr:region> tag to see
how a region is used (or referenced).
If the above is defined in "/regions/stock.jspx", then you need + </tr:panelHeader> + </tr:regionDef>
If the above is defined in "/regions/stock.jspx", then you need to register the above region in "WEB-INF/region-metadata.xml". Here's an example:
And after it is registered, you can use the above region in say "master.jspx", like this:
+ </tr:region>#{attrs.bar}
.
- Tag name: <af:resetActionListener>
+ Tag name: <tr:resetActionListener>
The resetActionListener tag is a declarative way to allow an action @@ -36,11 +36,11 @@ the all elements on the form will be reset before being applied. The resetModel actionListener will also be called.
+ <tr:resetActionListener/>
- Tag name: <af:returnActionListener>
+ Tag name: <tr:returnActionListener>
The returnActionListener tag is a declarative way to allow an action source @@ -38,25 +38,25 @@ There is also a "Cancel" button, which when clicked will close the dialog without returning a value.
+ </tr:table> + <tr:commandButton text="Cancel"> + <tr:returnActionListener/> + </tr:commandButton>
- Tag name: <af:setActionListener>
+ Tag name: <tr:setActionListener>
@@ -34,7 +34,7 @@ tag can be used both with ADF Faces commands and JSF standard tags. More generally, it can be used with any component at all that implements the standard ActionSource interface. - Note that JSF comes with a <af:setPropertyActionListener>, which + Note that JSF comes with a <tr:setPropertyActionListener>, which does exactly the same.
@@ -61,7 +61,7 @@
...
<h:column>
<h:commandButton value="Show..." action="showDetail" ..>
- <af:setActionListener from="#{row}"
+ <tr:setActionListener from="#{row}"
to="#{processScope.detail}"/>
</h:commandButton>
</h:column>
Modified: incubator/adffaces/branches/matzew-repackaging-trinidad-save/trinidad/trinidad-api/src/site/xdoc/tagdoc/af_validator.xml
URL: http://svn.apache.org/viewvc/incubator/adffaces/branches/matzew-repackaging-trinidad-save/trinidad/trinidad-api/src/site/xdoc/tagdoc/af_validator.xml?rev=426296&r1=426295&r2=426296&view=diff
==============================================================================
--- incubator/adffaces/branches/matzew-repackaging-trinidad-save/trinidad/trinidad-api/src/site/xdoc/tagdoc/af_validator.xml (original)
+++ incubator/adffaces/branches/matzew-repackaging-trinidad-save/trinidad/trinidad-api/src/site/xdoc/tagdoc/af_validator.xml Thu Jul 27 15:40:54 2006
@@ -16,12 +16,12 @@
-->
- Tag name: <af:validator>
+ Tag name: <tr:validator>
The validator tag is an implementation of the future JSF 1.2
@@ -36,9 +36,9 @@
"validatorId". This Validator is added to the component and also
assigned to the "binding" ValueBinding.
Example:
+ <tr:inputText value="#{mybean.ename}">
+ <tr:validator binding="#{mybean.validator"/>
+ </tr:inputText>
javax.faces.validator.Validator
.