Archive for September, 2010

Acrobat/Reader 9: xfa.host.getFocus() no longer works

Issue

When you use the xfa.host.getFocus() method in your form templates you may notice different behavior in Acrobat or Reader 9 compared to previous versions. The method doesn’t work, returns null, or returns the following error:

xfa.host.getFocus is not a function

Solution

Set the target version to 8.1 or later in the Default tab of the template properties in Designer. Or, use the AcrobatVersion parameter in the API. The AcrobatVersion parameter takes precedence over the definition in the template. However, you can use the AcrobatVersion value “Auto” to use the version defined in the templates.

Additional information

The getFocus() method was implemented in XFA 2.6 (Reader 8.1).  If the PDF is rendered with a target version less than 8.1, the call to getFocus doesn’t work.  The target version of a template is defined either:

  • in the XDP template using the Default tab under the template properties, or using the <?formServer defaultPDFRenderFormat acrobat8.1dynamic?> tag in the XML source
  • in the AcrobatVersion setting in the PDFFormRenderSpec when calling the renderPDFForm() method from the Forms API

There is one special case in Acrobat/Reader 8, which allows the call to getFocus() even if the target version is less than 8.1. Therefore, you do not need to use one of the solutions above for Acrobat or Reader 8.  This behavior is a bug in Acrobat 8 as it doesn’t respect the target version and relevant XFA definition. In Acrobat 9, the target version is respected.

reference: (181779861/2714554)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES 8.0.1.2: Workspace memory leak using IE6 or IE7

Issue

When you use Workspace ES 8.0.1.2 in Internet Explorer 6 or 7 and you log in, open an XFA form, and log out repeatedly, the memory usage increases. Usage increases between 500 KB to 3 MB when you close forms, and up to 30 MB when you log out of Workspace.

Solution

This is a bug in Workspace 8.0.1.2.  Contact Enterprise Support to obtain a patch for LiveCycle ES 8.0.1.2. Or, use LiveCycle ES 8.2.1.1 or later.

reference: (180457723/1906173)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: warning in server log when passivating document

Issue

A Form Guide stitches a PDF from multiple XDP fragments and then returns the PDF to the process in LiveCycle ES 8.2.1 or 9. When you submit this Form Guide, a warning appears in the server log:

[12/18/09 15:34:08:003 EST] 0000015a SystemOut
 O XDP form1.xdp,form2.xdp,form3.xdp,form4.xdp,form5.xdp,form6.xdp
[12/18/09 15:34:08:004 EST] 0000015a SystemOut O OPS form1.xdp
[12/18/09 15:34:08:234 EST] 0000015a AdobeCacheImp W com.adobe.repository.cache.AdobeCacheImpl put Document error while passivating document [<document state=”passive” senderVersion=”3″ persistent=”false” senderPersistent=”false” passivated=”true” senderPassivated=”true” deserialized=”true” senderHostId=”127.0.0.1/10.101.158.145″ callbackId=”0″ senderCallbackId=”4228″ callbackRef=”com.adobe.idp._IDocumentCallbackStub:

Solution

This warning is an informational message from the repository cache and can be ignored. In the ADEP platform (ES3) Adobe will downgrade this warning to an INFO or FINE level message, so it doesn’t appear in the logs.

reference: (181308950/2523516)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES2: PDF file size bloat using FormDataIntegration importData method

Issue

When you export data with the exportData method of the FormDataIntegration Service, and then import the data using importData, the PDF file size increases dramatically.  This problem does not occur if you use the import and export options in Acrobat, or use LiveCycle ES 8.2.1 SP3.

Solution

This is a bug in LiveCycle ES2 SP1.  Update to LiveCycle ES2 SP2 or later.  You can also contact Enterprise Support if you require a patch for LiveCycle ES2 SP1 9.0.0.1.

reference: (181664835/2660679)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES2: ALC-PDG-001-026 – transaction timeout settings not respected for watched folders

Issue

When you use watched folders with PDFG ES2 SP1 and increase the timeout, the process still times out after the default 600 seconds. This problem will occur even if you have increased the Application Server transaction timeout, the socket timeout, or JTA timeout in jboss-server.xml, or the timeout settings on the PDFConfigService, and ConvertPDFService.

This problem can be seen with the following log extract:

2010-08-09 08:36:50,485 INFO [com.adobe.pdfg.BMCCaller] ALC-PDG-001-026 133MB File.pdf: Time of Job Execution: 635,047 ms for job = 133MBFile.pdf3f45fc-272597-26ad04-89f5d7-039852-037534

2010-08-09 08:36:50,485 ERROR [com.adobe.pdfg.GeneratePDFImpl] ALC-PDG-001-000
ALC-PDG-010-010-The conversion has timed out.

2010-08-09 08:36:50,485 ERROR [com.adobe.idp.jobmanager.execution.workadapter.PersistentExecutableJob] 
PeristentExecutableJob:execute():Attempting to fail job. Reason:

Solution

This is a bug in PDFG ES2 SP1.  Update to LiveCycle ES2 SP2 or later. You can also contact Enterprise Support if you require a patch for LiveCycle ES2 SP1 9.0.0.1.

reference: (181707812/2686855)

 

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES2: java.net.ProtocolException using password protected WSDL

Issue

When you try to load a password-protected WSDL using the WebService service in LiveCycle ES2 (9.0.0.0), the following exception occurs:

java.net.ProtocolException thrown: Server redirected too many times (20)

Solution

This is a bug in LC ES2.  Update to LiveCycle ES2 SP1 or later.  Contact Enterprise Support if you require a patch for LiveCycle ES2 (9.0.0.0).

reference: (2466491)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)