LiveCycle Doc team

Recently, when I was automating a process, part of the requirement was to merge XML data with a form design that was created in Adobe LiveCycle Designer ES. When you are merging a form design with data from an XML file, you can use either the Forms service or Output service in LiveCycle ES. Depending on how you use the resultant merged form design and data, determines which service best meets your requirements.

Continue reading "Should I use the Output service or Forms service?" »

Posted by Gilbert Yu at 12:32 PM | Permalink | Comments (0)

Recently, I was developing a LiveCycle ES component that uses Java APIs that are new to me. As I was thinking about how to implement the functionality that these new APIs offered into a LiveCycle ES component, a development pattern occurred to me. This pattern can be used by any LiveCycle ES component developer.

Because a LiveCycle ES component runs as a service, there isn't an easy way to debug the application logic. That is, how can I set a breakpoint in the Java code and step through it? How can I ensure that these APIs are doing what they are supposed to do?

The answer is to use Java APIs inside a test Java console application. Then, you can set a breakpoint and step through your Java application logic to ensure the application logic works properly. Once you are satisfied the application works, copy the application logic from your test Java project to your Java project that creates a custom component.

This worked for me. The new Java APIs I was using were proxy Java APIs that consume a web service that returns real-time weather information. That is right - I wanted to embed a custom service into LiveCycle ES that returns real-time weather information so I can embed weather information into a PDF document. And using this pattern, I was able to ensure that the Java APIs worked before I used them inside a LiveCycle ES component.

Note: If you are interested in knowing how to create a custom LiveCycle ES component that invokes an external web service, then keep an eye out for a future development article titled Invoking Web Services using Custom Components to appear on the LiveCycle ES developer center. As a component developer, this is an article you won't want to miss.

Posted by Scott MacDonald at 2:00 PM | Permalink | Comments (0)

Did you know that you can use JAX-WS to create Java proxy classes that consume the SOAP stack of a LiveCycle ES 8.2 service? That is correct, you have another choice when deciding how best to invoke LiveCycle ES from a Java client application.

When creating proxy classes, you do not need to include LiveCycle Java client JAR files in your Java project's class path.  For example, assume you want to invoke the Encryption service to protect a PDF document with password-based encryption.

Continue reading "Invoking LiveCycle ES 8.2 services using Java proxy files created using JAX-WS" »

Posted by Scott MacDonald at 4:12 PM | Permalink | Comments (0)

Earlier this week, Adobe launched the Adobe Flash Builder 4 beta program. Flash Builder 4, which is the next evolution of Adobe Flex Builder, includes a long list of feature improvements, new data-centric development features, and a new design-develop workflow with the new Adobe Flash Catalyst.

Continue reading "Adobe Flash Builder 4 Beta: Get it while it’s hot!" »

Posted by Alex Mitchell at 11:28 AM | Permalink | Comments (0)

The Rights Management service tracks specific actions as they occur, such as when a policy is used to protect a PDF document or when a policy-protected document is opened. You can develop client applications that are able to search for Rights Management events. Because the Rights Management service exposes a public WSDL, you can create a proxy library that consumes the WSDL and use the proxy library in client applications built with development environments that support web services such as Microsoft Visual Studio.

When creating a proxy library that consumes that Rights Management WSDL, the proxy library has access to data types exposed by the Rights Management WSDL. These data types include EventSpec and AuditSpec. For more information, see Searching for Events.

Posted by Scott MacDonald at 10:36 AM | Permalink | Comments (0)