Forms Service API Quick Starts

The following Quick Starts are available for the Forms service:

Description	Java API (EJB Mode)	Web service API (Java Base64)	Web service API (MTOM)
Rendering Interactive PDF Forms	Quick Start (EJB mode): Rendering an interactive PDF form using the Java API	Quick Start (Base64): Rendering an interactive PDF form using the web service API	Quick Start (MTOM): Rendering an interactive PDF document using the web service API
Rendering Forms at the Client	Quick Start (EJB mode): Rendering a form at the client using the Java API	Quick Start (Base64): Rendering a form at the client using the web service API	Not available
Rendering Forms Based on Fragments	Quick Start (EJB mode): Rendering a form based on fragments using the Java API	Quick Start (Base64): Rendering a form based on fragments using the web service API	Not available
Rendering Rights-Enabled Forms	Quick Start (EJB mode): Rendering a rights-enabled form using the Java API	Quick Start (Base64): Rendering a rights-enabled form using the web service API	Not available
Rendering Forms as HTML	Quick Start (EJB mode): Rendering an HTML form using the Java API	Quick Start (Base64): Rendering an HTML form using the web service API	Not available
Rendering HTML Forms Using Custom CSS Files	Quick Start (EJB mode): Rendering an HTML Form with a custom toolbar using the Java API	Quick Start (Base64): Rendering an HTML form that uses a CSS file using the web service API	Not available
Rendering HTML Forms with Custom Toolbars	Quick Start (EJB mode): Rendering an HTML Form with a custom toolbar using the Java API	Quick Start (Base64): Rendering an HTML Form with a custom toolbar using the web service API	Not available
Handling Submitted Forms (XML data submitted from a PDF form)	Quick Start (EJB mode): Handling PDF forms submitted as XML using the Java API	Quick Start (Base64): Handling submitted forms using the web service API	Not available
Handling Submitted Forms (PDF data submitted from a PDF form)	Quick Start (EJB mode): Handling PDF forms submitted as PDF using the Java API	Not available	Not available
Handling Submitted Forms (XML data submitted from an HTML form)	Quick Start (EJB mode): Handling HTML forms submitted as XML using the Java API	Not available	Not available
Creating PDF Documents with Submitted XML Data	Quick Start (EJB mode): Creating PDF Documents with submitted XML data using the Java API	Not available	Not available
Prepopulating Forms with Flowable Layouts	Quick Start (EJB mode): Prepopulating Forms with Flowable Layouts using the Java API	Quick Start (Base64): Prepopulating Forms with Flowable Layouts using the web service API	Not available
Calculating Form Data	Quick Start (EJB mode): Handling a form containing a calculation script using the Java API	Quick Start (Base64): Handling a form containing a calculation script using web service API	Not available
Optimizing the Performance of the Forms Service	Quick Start (EJB mode): Optimizing performance using the Java API	Quick Start (Base64): Optimizing performance using the web service API	Not available
Rendering Forms By Value	Quick Start (EJB mode): Rendering by value using the Java API	Quick Start (Base64): Rendering by value using the web service API	Not available
Passing Documents to the Forms Service	Quick Start (EJB mode): Passing documents to the Forms Service using the Java API	Not available	Quick Start (MTOM): Passing documents to the Forms Service using the web service API

Application logic that uses the Forms service API is implemented as Java servlets. LiveCycle operations are organized into the following Quick Start categories:

Java API (EJB) - Demonstrates using the LiveCycle strongly-typed API and the connection mode is set to EJB. All of these quick starts are implemented as Java servlets. (See Setting connection properties.)
Web service API (Base64) - Demonstrates using Java proxy classes and Base64. These Java proxy classes are separate from the LiveCycle strongly-typed API. All of these quick starts are implemented as Java servlets.(See Invoking LiveCycle using Base64 encoding.)
Web service API (MTOM) - Demonstrates using a .NET client proxy and MTOM. These quick starts are implemented as .NET console applications. (See Invoking LiveCycle using MTOM.)

Note: Quick starts located in Programming with v are based on the LiveCycle Server being deployed on JBoss and the Windows operating system. However, if you are using another operating system, such as Unix, replace windows specific paths with paths supported by the applicable operating system. Likewise, if you are using another J2EE application server, then ensure that you specify valid connection properties. (See Setting connection properties.)

The Adobe Developer web site contains the following article that discusses how to create a ASP.NET application that invokes the Forms service and renders forms. See Creating form rendering ASP.NET applications.