However, as of version 5. In , Lowagie disbanded the rugPdf code and wrote the new library named iText. In the summer of , Paulo Soares joined the project and is now considered one of the main developers. In late , iText became available for proprietary license, and in early iText Software Corp. While it has a separate codebase, it is synchronized to the main iText release schedule.
|Published (Last):||5 October 2008|
|PDF File Size:||13.26 Mb|
|ePub File Size:||12.29 Mb|
|Price:||Free* [*Free Regsitration Required]|
Seam now includes a component set for generating documents using iText. To include PDF support in your application, included jboss-seam-pdf. There is no further configuration needed to use Seam's ciText supportfon. The Seam iText module requires the use of Facelets as the view technology. Future versions of the library may also support the use of JSP.
Additionally, it requires the use of the seam-ui package. It demonstrates proper deployment packaging, and it contains a number examples that demonstrate the key PDF generation features current supported. Documents should always have the document tag at the root of the document.
A full list of supported pages sizes can be found in com. PageSize class. Alternatively, pageSize can provide the width and height of the page directly. Valid values are portrait and landscape. In landscape mode, the height and width page size values are reversed. Valid values are inline , which indicates the document should be displayed in the browser window if possible, and attachment , which indicates that the document should be treated as a download.
The default value is inline. Useful documents will need to contain more than just text; however, the standard UI components are geared towards HTML generation and are not useful for generating PDF content. Most uses of text should be sectioned into paragraphs so that text fragments can be flowed, formatted and styled in logical groups. The text tag allows text fragments to be produced from application data using normal JSF converter mechanisms.
This will typically be a value binding expression. 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.
Image object. This can be expressed as a single percentage value or as two percentage values representing separate x and y scaling percentages. It supports the following attributes:. 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.
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. 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. Sections can only be used inside of chapters, but they may be nested arbitrarily deep.
Most PDF viewers provide easy navigation between chapters and sections in a document. Every chapter should be assigned a chapter number. The fourth section of of the first section of chapter three would be section 3. To omit the chapter number, a number depth of 2 should be used. In that case, the section number would be displayed as 1. Any chapter or section can contain a p:title. The body of the title may contain raw text or may be a p:paragraph.
List structures can be displayed using the p:list and p:listItem tags. Lists may contain arbitrarily-nested sublists. List items may not be used outside of a list. If no style is given, the list items are bulleted. Table structures can be created using the p:table and p:cell tags. Unlike many table structures, there is no explicit row declaration. If a table has 3 columns, then every 3 cells will automatically form a row. Header and footer rows can be declared, and the headers and footers will be repeated in the event a table structure spans multiple pages.
There should be one value for each column. This value is subtracted from the headerRows value. If document has 2 rows which make up the header and one row that makes up the footer, headerRows should be set to 3 and footerRows should be set to 1. Tables do not have the ability to span across multiple rows.
Seam documents do not yet support a full color specification. Currently, only named colors are supported. They are: white , gray , lightgray , darkgray , black , red , pink , yellow , green , magenta , cyan and blue. Where alignment values are used, the Seam PDF supports the following horizontal alignment values: left , right , center , justify and justifyall. The vertical alignment values are top , middle , bottom , and baseline.
Document generation works out of the box with no additional configuration needed. However, there are a few points of configuration that are needed for more serious applications.
This capability requires some configuration. The use-extensions option on the document store component completes the functionality by instructing the document store to generate URLs with the correct filename extension for the document type being generated.
Generated documents are stored in conversation scope and will expire when the conversation ends. At that point, references to the document will be invalid. To You can specify a default view to be shown when a document does not exist using the error-page property of the documentStore.
Charting support is also provided with jboss-seam-pdf. Charting requires the JFreeChart library jfreechart. Three types of charts are currently supported: pie charts, bar charts and line charts.
It should be a number between 0 completely transparent and 1 completely opaque. Default value is true. If this is null, the background is not filled. If false, the chart is drawn as an ellipse. The default is true. One of: clockwise or anticlockwise. The default is clockwise. Category data can be broken down into series. The series tag is used to categorize a set of data with a series and apply styling to the entire series.
The color component declares a color or gradient than can be referenced when drawing filled shapes. For gradient colors, this the starting color. Valid values are butt , round and square. Valid values are miter , round and bevel.
The space separated integers indicate the length of each alternating drawn and undrawn segments. Seam can use iText to generate barcodes in a wide variety of formats. These barcodes can be embedded in a PDF document or displayed as an image on a web page. Note that when used with HTML images, barcodes can not currently display barcode text in the barcode.
Seam now provides experimental support for rendering Swing components to into a PDF image. Some Swing look and feels supports, notably ones that use native widgets, will not render correctly.
The height of the component to be rendered. Using PDF Support Creating a document Basic Text Elements Headers and Footers Chapters and Sections Lists Tables Document Constants Configuring iText Charting Bar codes Further documentation.
Subscribe to RSS
Seam now includes an component set for generating documents using iText. To include PDF support in your application, included jboss-seam-pdf. There is no further configuration needed to use Seam's iText supportfon. The Seam iText module requires the use of Facelets as the view technology. Future versions of the library may also support the use of JSP. Additionally, it requires the use of the seam-ui package. It demonstrates proper deployment packaging, and it contains a number examples that demonstrate the key PDF generation features current supported.
Chapter 18. iText PDF generation
Seam now includes a component set for generating documents with iText. Using PDF Support. To include PDF support in your application, place jboss-seam-pdf. No further configuration is required to use Seam's iText support. The Seam iText module requires that Facelets be used as the view technology.
Seam now includes a component set for generating documents using iText. To include PDF support in your application, put jboss-seam-pdf. There is no further configuration needed to use Seam's iText support. The Seam iText module requires the use of Facelets as the view technology.