Archive for March, 2009

LiveCycle ReaderExtensions7: ClassCastException trying to deploy the sample application

Issue

 When trying to deploy the sample ReaderExtensions application to the application server you may receive the following exception:

java.lang.ClassCastException
 at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(Unknown Source)

Reason

 This is caused by the DocumentServicesLibrary.jar which appears in too many places in the ear files. It should not have been included in LiveCycle-security.ear file.

Solution

Workaround 1:

If you already have LiveCycle 7.2 installed, then all you need to do is edit customAssembly.xml in the components\pdfagent and delete the line with DocumentServicesLibrary.jar in it. Run LCM and redeploy.

Workaround 2:

Include AdobeCSAUtils.jar in your project and use:

connectionfactory = Utilities.serviceLookup("DataManagerService"); 
DataManager dataManager = DataManagerHelper.narrow((org.omg.CORBA.Object)connectionfactory.getConnection()); 
connectionfactory = Utilities.serviceLookup("PDFManipulation"); 
PDFFactory pdfFactory = PDFFactoryHelper.narrow((org.omg.CORBA.Object)connectionfactory.getConnection());

________________________________________
reference: (1-32712143)

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

LiveCycle Forms7: FormServerException: java.lang.IlgalStateException: Connection to failed service

Issue

 FormsIVS was installed and working fine on one Solaris box.  When trying to use the FormsIVS interface from other Solaris boxes the following exception occured:

com.adobe.formServer.interfaces.RenderFormException:

com.adobe.formServer.interfaces.FormServerException: java.lang.IlgalStateException: Connection to failed service.

at ros.core.technicalservices.service.docgen.ejb.impl.DocumentGenerationManagerBean.generateViewablePDF

Reason

 This is because the following packages were not installed on the other Solaris servers:

SUNWxwplt, SUNWxwpltx, SUNWxwrtl, SUNWxwrtx

These pacakages install libX11.so.4 into:

/usr/openwin/lib

/usr/openwin/sparcv9/lib

/usr/lib/

/usr/lib/sparcv9

Solution

 Installing these packages to the other Solaris servers, and making sure the file is on the classpath will resolve the issue.

reference: (1-32957277)

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

LiveCycle PDFG7: Error 1009 trying to start application server

Issue

 If you have installed PDF Generator 7, you may receive the following error when trying to start the application server service:

Error 1009

Reason

 You must use the same user to install MS Word and PDFG, and this user must be the same user account used to start the application server service.

Solution

 Re-install MS Word and PDFG using the same user account (this should be an Administrative user), and then change the LogOn properties for the application server service in the Control Panel to use this account to start the service.

reference: (1-32085976)

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

LiveCycle Designer7.1: field re-sizing not working for left-handed mouse users

Issue

 When switching mouse Primary and Secondary Buttons (i.e. from right-hand to left-hand setup), you will not be able to change a field size with the mouse.

1-Switch the mouse primary and secondary buttons:

Click on Windows Start Button -> Control Panel -> Select Mouse -> Tick “Switch Primary and Secondary Buttons” -> click Apply and then OK

2-Create a new form with Designer 7.1 and add a text field

3-Try to change the text field’s size with the mouse. This will not work.

It is expected that the field’s size can be changed by left handed users

Reason

This is a bug in Designer 7.1.

Solution

This has been fixed in Designer 8.0. and later.

reference: (1-28063550/1341841)

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

Acrobat/Reader 7: using loadXML() to load data can result in an Acrobat crash

Issue

 If you are using loadXML() to load data into a PDF, where the XML contains attributes like “nill=true”, then you may experience an application crash in Acrobat/Reader 7.

For example, if you use Javascript code in your form similar to:

------Form.page1.Button1::click - (JavaScript, client) -----------
try {
    xfa.record.FORM.loadXML(xfa.resolveNode("FORM.page1.txtXMLData").rawValue, true, true);
    xfa.form.remerge();
} catch(err) {
    xfa.host.messageBox("Exception:" + err.name + " - " + err.message);
}

where textXMLData contains the following data:

<?xml version="1.0" encoding="UTF-8"?>
<FORM xmlns="http://www.company.com/testNil" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <CaseManagement>
 <CaseInitiationDate xsi:nil="true" />
 ...
 </CaseManagement>
</FORM>

Reason

 This is a bug in Acrobat/Reader 7.

Solution

 This bug has been fixed in Acrobat/Reader 8.

There is also a simple workaround to this problem:

On the form itself, ensure that the  “attributes” data loading option is set to ignore as follows:

<config>  <present>  <common>  <data>  <attributes>ignore</attributes>  </data> ... 

__________________________________________

reference: (1-16996911/1266068)

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

LiveCycle ES: “DocumentBuilder returned is not DOM3 compliant, using Xerces’s DOM parser” warning

Issue

After installing LiveCycle ES Update 1 SP2 with WebSphere 6.1 as the application server, you may observe the following warnings in the SystemOut.log:

[06.03.09 11:21:40:015 CET] 0000002d SAMLToken W com.adobe.idp.common.errors.Logger$LogConsumer run UserM:GENERIC_WARNING:
[Thread Hashcode: 1753770120] DocumentBuilder returned is not DOM3 compliant, using Xerces's DOM parser

[06.03.09 11:21:45:140 CET] 000000be Reference I org.apache.xml.security.signature.Reference verify
Verification successful for URI "#d143154d8548fe37c847df7490b054cc"

Reason

This warning message is logged if the XML parser available to LiveCycle ES is not DOM 3 compliant. This warning has been reported on some Websphere installations, but seems to have been resolved in the latest fixpacks from IBM.

Solution

Upgrade to the latest WebSphere fixpack.  You can suppress the warning in the log by setting the log level for com.adobe.idp.um.businesslogic.authentication.SAMLToken to “ERROR”.

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