Developing SPIs for LiveCycle ES > Creating Custom Authentication Providers > Packaging the authentication provider

Packaging the authentication provider
Before deploying the authentication provider to LiveCycle ES, you must first package your Eclipse project into a JAR file. Also, the component XML file and the external JAR files on which the authentication provider’s business logic depends are present. Also, the component XML file must be present. The component.xml file and external JAR files must be located at the root of the JAR file.
The following illustration shows the Eclipse project’s content that is packaged into the custom authentication provider’s JAR file.
You must package the authentication provider into a JAR file named adobe-authentication-spi-dsc.jar. In the previous diagram, notice that .JAVA files are listed. Once packaged into a JAR file, the corresponding .CLASS files must also be specified. Without the .CLASS files, the authentication provider does not work.
Note: After you package the authentication provider into a JAR file, you can deploy the component to LiveCycle ES. (See Deploying your component.)
Note: You can also programmatically deploy a component. (See Programmatically Deploying Components.)

Developing SPIs for LiveCycle ES > Creating Custom Authentication Providers > Packaging the authentication provider

Programming with LiveCycle ES (LiveDocs)
Adobe LiveCycle ES Update 1

 

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/000922.html