[jbosstools-commits] JBoss Tools SVN: r23881 - trunk/jst/plugins/org.jboss.tools.jst.web.kb/taglibs.

Author: dazarov Date: 2010-08-03 12:07:13 -0400 (Tue, 03 Aug 2010) New Revision: 23881 Modified: trunk/jst/plugins/org.jboss.tools.jst.web.kb/taglibs/SeamPdf.xml Log: https://jira.jboss.org/browse/JBIDE-5231 Modified: trunk/jst/plugins/org.jboss.tools.jst.web.kb/taglibs/SeamPdf.xml =================================================================== --- trunk/jst/plugins/org.jboss.tools.jst.web.kb/taglibs/SeamPdf.xml 2010-08-03 16:02:51 UTC (rev 23880) +++ trunk/jst/plugins/org.jboss.tools.jst.web.kb/taglibs/SeamPdf.xml 2010-08-03 16:07:13 UTC (rev 23881) @@ -3,9 +3,9 @@ <tag-lib defaultPrefix="p"> <component name="document"> - <description><CDATA[Documents are generated by facelets documents using tags in the http://jboss.com/products/seam/pdf namespace. Documents should always have the document tag at the root of the document. The document tag prepares Seam to generate a document into the DocumentStore and renders an HTML redirect to that stored content.]CDATA></description> + <description>Documents are generated by facelets documents using tags in the http://jboss.com/products/seam/pdf namespace. Documents should always have the document tag at the root of the document. The document tag prepares Seam to generate a document into the DocumentStore and renders an HTML redirect to that stored content.</description> <attribute name="type"> - <description><CDATA[The type of the document to be produced. Valid values are PDF, RTF and HTML modes. Seam defaults to PDF generation, and many of the features only work correctly when generating PDF documents.]CDATA></description> + <description>The type of the document to be produced. Valid values are PDF, RTF and HTML modes. Seam defaults to PDF generation, and many of the features only work correctly when generating PDF documents.</description> <proposal type="enumeration"> <param value="PDF" /> <param value="RTF" /> @@ -13,24 +13,24 @@ </proposal> </attribute> <attribute name="pageSize"> - <description><CDATA[The size of the page to be generate. The most commonly used values would be LETTER and A4. A full list of supported pages sizes can be found in com.lowagie.text.PageSize class. Alternatively, pageSize can provide the width and height of the page directly. The value "612 792", for example, is equivalent to the LETTER page size.]CDATA></description> + <description>The size of the page to be generate. The most commonly used values would be LETTER and A4. A full list of supported pages sizes can be found in com.lowagie.text.PageSize class. Alternatively, pageSize can provide the width and height of the page directly. The value "612 792", for example, is equivalent to the LETTER page size.</description> <proposal type="enumeration"> <param value="LETTER" /> <param value="A4" /> </proposal> </attribute> <attribute name="orientation"> - <description><CDATA[The orientation of the page. Valid values are portrait and landscape. In landscape mode, the height and width page size values are reversed.]CDATA></description> + <description>The orientation of the page. Valid values are portrait and landscape. In landscape mode, the height and width page size values are reversed.</description> <proposal type="enumeration"> <param value="portrait" /> <param value="landscape" /> </proposal> </attribute> <attribute name="margins"> - <description><CDATA[The left, right, top and bottom margin values.]CDATA></description> + <description>The left, right, top and bottom margin values.</description> </attribute> <attribute name="marginMirroring"> - <description><CDATA[Indicates that margin settings should be reversed an alternating pages.]CDATA></description> + <description>Indicates that margin settings should be reversed an alternating pages.</description> </attribute> <attribute name="title" /> <attribute name="subject" /> @@ -40,16 +40,16 @@ </component> <component name="paragraph"> - <description><CDATA[Most uses of text should be sectioned into paragraphs so that text fragments can be flowed, formatted and styled in logical groups.]CDATA></description> + <description>Most uses of text should be sectioned into paragraphs so that text fragments can be flowed, formatted and styled in logical groups.</description> <attribute name="firstLineIndent" /> <attribute name="extraParagraphSpace" /> <attribute name="leading" /> <attribute name="multipliedLeading" /> <attribute name="spacingBefore"> - <description><CDATA[The blank space to be inserted before the element.]CDATA></description> + <description>The blank space to be inserted before the element.</description> </attribute> <attribute name="spacingAfter"> - <description><CDATA[The blank space to be inserted after the element.]CDATA></description> + <description>The blank space to be inserted after the element.</description> </attribute> <attribute name="indentationLeft" /> <attribute name="indentationRight" /> @@ -57,22 +57,22 @@ </component> <component name="text"> - <description><CDATA[The text tag allows text fragments to be produced from application data using normal JSF converter mechanisms. It is very similar to the outputText tag used when rendering HTML documents.]CDATA></description> + <description>The text tag allows text fragments to be produced from application data using normal JSF converter mechanisms. It is very similar to the outputText tag used when rendering HTML documents.</description> <attribute name="value"> - <description><CDATA[The value to be displayed. This will typically be a value binding expression.]CDATA></description> + <description>The value to be displayed. This will typically be a value binding expression.</description> </attribute> </component> <component name="font"> - <description><CDATA[The font tag defines the default font to be used for all text inside of it.]CDATA></description> + <description>The font tag defines the default font to be used for all text inside of it.</description> <attribute name="name"> - <description><CDATA[The font name, for example: COURIER, HELVETICA, TIMES-ROMAN, SYMBOL or ZAPFDINGBATS.]CDATA></description> + <description>The font name, for example: COURIER, HELVETICA, TIMES-ROMAN, SYMBOL or ZAPFDINGBATS.</description> </attribute> <attribute name="size"> - <description><CDATA[The point size of the font.]CDATA></description> + <description>The point size of the font.</description> </attribute> <attribute name="style"> - <description><CDATA[The font styles. Any combination of : NORMAL, BOLD, ITALIC, OBLIQUE, UNDERLINE, LINE-THROUGH]CDATA></description> + <description>The font styles. Any combination of : NORMAL, BOLD, ITALIC, OBLIQUE, UNDERLINE, LINE-THROUGH</description> <proposal type="enumeration"> <param value="NORMAL" /> <param value="BOLD" /> @@ -83,31 +83,31 @@ </proposal> </attribute> <attribute name="encoding"> - <description><CDATA[The character set encoding.]CDATA></description> + <description>The character set encoding.</description> </attribute> </component> <component name="newPage"> - <description><CDATA[p:newPage inserts a page break.]CDATA></description> + <description>p:newPage inserts a page break.</description> </component> <component name="image"> - <description><CDATA[p:image inserts an image into the document. Images can be be loaded from the classpath or from the web application context using the value attribute. -Resources can also be dynamically generated by application code. The imageData attribute can specify a value binding expression whose value is a java.awt.Image object.]CDATA></description> + <description>p:image inserts an image into the document. Images can be be loaded from the classpath or from the web application context using the value attribute. +Resources can also be dynamically generated by application code. The imageData attribute can specify a value binding expression whose value is a java.awt.Image object.</description> <attribute name="value"> - <description><CDATA[A resource name or a method expression binding to an application-generated image.]CDATA></description> + <description>A resource name or a method expression binding to an application-generated image.</description> </attribute> <attribute name="rotation"> - <description><CDATA[The rotation of the image in degrees.]CDATA></description> + <description>The rotation of the image in degrees.</description> </attribute> <attribute name="height"> - <description><CDATA[The height of the image.]CDATA></description> + <description>The height of the image.</description> </attribute> <attribute name="width"> - <description><CDATA[The width of the image.]CDATA></description> + <description>The width of the image.</description> </attribute> <attribute name="alignment"> - <description><CDATA[The alignment of the image. Seam PDF supports the following horizontal alignment values: left, right, center, justify and justifyall. The vertical alignment values are top, middle, bottom, and baseline.]CDATA></description> + <description>The alignment of the image. Seam PDF supports the following horizontal alignment values: left, right, center, justify and justifyall. The vertical alignment values are top, middle, bottom, and baseline.</description> <proposal type="enumeration"> <param value="left" /> <param value="right" /> @@ -121,40 +121,40 @@ </proposal> </attribute> <attribute name="alt"> - <description><CDATA[Alternative text representation for the image.]CDATA></description> + <description>Alternative text representation for the image.</description> </attribute> <attribute name="indentationLeft" /> <attribute name="indentationRight" /> <attribute name="spacingBefore"> - <description><CDATA[The blank space to be inserted before the element.]CDATA></description> + <description>The blank space to be inserted before the element.</description> </attribute> <attribute name="spacingAfter"> - <description><CDATA[The blank space to be inserted after the element.]CDATA></description> + <description>The blank space to be inserted after the element.</description> </attribute> <attribute name="widthPercentage" /> <attribute name="initialRotation" /> <attribute name="dpi" /> <attribute name="scalePercent"> - <description><CDATA[The scaling factor (as a percentage) to use for the image. This can be expressed as a single percentage value or as two percentage values representing separate x and y scaling percentages.]CDATA></description> + <description>The scaling factor (as a percentage) to use for the image. This can be expressed as a single percentage value or as two percentage values representing separate x and y scaling percentages.</description> </attribute> <attribute name="wrap" /> <attribute name="underlying" /> </component> <component name="anchor"> - <description><CDATA[p:anchor defines clickable links from a document.]CDATA></description> + <description>p:anchor defines clickable links from a document.</description> <attribute name="name"> - <description><CDATA[The name of an in-document anchor destination.]CDATA></description> + <description>The name of an in-document anchor destination.</description> </attribute> <attribute name="reference"> - <description><CDATA[The destination the link refers to. Links to other points in the document should begin with a "#". For example, "#link1" to refer to an anchor postion with a name of link1. Links may also be a full URL to point to a resource outside of the document.]CDATA></description> + <description>The destination the link refers to. Links to other points in the document should begin with a "#". For example, "#link1" to refer to an anchor postion with a name of link1. Links may also be a full URL to point to a resource outside of the document.</description> </attribute> </component> <component name="header"> - <description><CDATA[The p:header and p:footer components provide the ability to place header and footer text on each page of a generated document, with the exception of the first page. Header and footer declarations should appear near the top of a document.]CDATA></description> + <description>The p:header and p:footer components provide the ability to place header and footer text on each page of a generated document, with the exception of the first page. Header and footer declarations should appear near the top of a document.</description> <attribute name="alignment"> - <description><CDATA[The alignment of the image. Seam PDF supports the following horizontal alignment values: left, right, center, justify and justifyall. The vertical alignment values are top, middle, bottom, and baseline.]CDATA></description> + <description>The alignment of the image. Seam PDF supports the following horizontal alignment values: left, right, center, justify and justifyall. The vertical alignment values are top, middle, bottom, and baseline.</description> <proposal type="enumeration"> <param value="left" /> <param value="right" /> @@ -168,7 +168,7 @@ </proposal> </attribute> <attribute name="backgroundColor"> - <description><CDATA[The background color of the header/footer box. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>The background color of the header/footer box. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -185,7 +185,7 @@ </proposal> </attribute> <attribute name="borderColor"> - <description><CDATA[The border color of the header/footer box. Individual border sides can be set using borderColorLeft, borderColorRight, borderColorTop and borderColorBottom. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>The border color of the header/footer box. Individual border sides can be set using borderColorLeft, borderColorRight, borderColorTop and borderColorBottom. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -202,7 +202,7 @@ </proposal> </attribute> <attribute name="borderColorLeft"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -219,7 +219,7 @@ </proposal> </attribute> <attribute name="borderColorRight"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -236,7 +236,7 @@ </proposal> </attribute> <attribute name="borderColorTop"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -253,7 +253,7 @@ </proposal> </attribute> <attribute name="borderColorBottom"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -270,7 +270,7 @@ </proposal> </attribute> <attribute name="borderWidth"> - <description><CDATA[The width of the border. Inidvidual border sides can be specified using borderWidthLeft, borderWidthRight, borderWidthTop and borderWidthBottom.]CDATA></description> + <description>The width of the border. Inidvidual border sides can be specified using borderWidthLeft, borderWidthRight, borderWidthTop and borderWidthBottom.</description> </attribute> <attribute name="borderWidthLeft" /> <attribute name="borderWidthRight" /> @@ -279,9 +279,9 @@ </component> <component name="footer"> - <description><CDATA[The p:header and p:footer components provide the ability to place header and footer text on each page of a generated document, with the exception of the first page. Header and footer declarations should appear near the top of a document.]CDATA></description> + <description>The p:header and p:footer components provide the ability to place header and footer text on each page of a generated document, with the exception of the first page. Header and footer declarations should appear near the top of a document.</description> <attribute name="alignment"> - <description><CDATA[The alignment of the image. Seam PDF supports the following horizontal alignment values: left, right, center, justify and justifyall. The vertical alignment values are top, middle, bottom, and baseline.]CDATA></description> + <description>The alignment of the image. Seam PDF supports the following horizontal alignment values: left, right, center, justify and justifyall. The vertical alignment values are top, middle, bottom, and baseline.</description> <proposal type="enumeration"> <param value="left" /> <param value="right" /> @@ -295,7 +295,7 @@ </proposal> </attribute> <attribute name="backgroundColor"> - <description><CDATA[The background color of the header/footer box. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>The background color of the header/footer box. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -312,7 +312,7 @@ </proposal> </attribute> <attribute name="borderColor"> - <description><CDATA[The border color of the header/footer box. Individual border sides can be set using borderColorLeft, borderColorRight, borderColorTop and borderColorBottom. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>The border color of the header/footer box. Individual border sides can be set using borderColorLeft, borderColorRight, borderColorTop and borderColorBottom. Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -329,7 +329,7 @@ </proposal> </attribute> <attribute name="borderColorLeft"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -346,7 +346,7 @@ </proposal> </attribute> <attribute name="borderColorRight"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -363,7 +363,7 @@ </proposal> </attribute> <attribute name="borderColorTop"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -380,7 +380,7 @@ </proposal> </attribute> <attribute name="borderColorBottom"> - <description><CDATA[Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.]CDATA></description> + <description>Currently, only named colors are supported. They are: white, gray, lightgray, darkgray, black, red, pink, yellow, green, magenta, cyan and blue.</description> <proposal type="enumeration"> <param value="white" /> <param value="gray" /> @@ -397,7 +397,7 @@ </proposal> </attribute> <attribute name="borderWidth"> - <description><CDATA[The width of the border. Inidvidual border sides can be specified using borderWidthLeft, borderWidthRight, borderWidthTop and borderWidthBottom.]CDATA></description> + <description>The width of the border. Inidvidual border sides can be specified using borderWidthLeft, borderWidthRight, borderWidthTop and borderWidthBottom.</description> </attribute> <attribute name="borderWidthLeft" /> <attribute name="borderWidthRight" /> @@ -406,7 +406,7 @@ </component> <component name="pageNumber"> - <description><CDATA[The current page number can be placed inside of a header or footer using the p:pageNumber tag. The page number tag can only be used in the context of a header or footer and can only be used once.]CDATA></description> + <description>The current page number can be placed inside of a header or footer using the p:pageNumber tag. The page number tag can only be used in the context of a header or footer and can only be used once.</description> </component> </tag-lib> \ No newline at end of file