Skip navigation
(ashwini_dash)
Currently Being Moderated

capturing the attributes of PDF elements

Sep 17, 2006 9:33 PM

hi,
i want to capture the attributes of each object of a PDF documents.Can anyone guide me which document i have to follow or any sample which can help me?
Ashwini
4384 Views   11 Replies   Latest reply: (scott_jiang), Oct 23, 2006 10:14 AM
 
Replies
  • HowardTreisman
    Currently Being Moderated
    1. HowardTreisman,
    Sep 18, 2006 4:08 PM   in reply to (ashwini_dash)
    Report
    Hi Ashwini

    This is a very broad question. Could you try to be more specific please.
    Howard
     
    |
    Mark as:
  • Currently Being Moderated
    2. (scott_jiang),
    Oct 16, 2006 11:21 AM   in reply to (ashwini_dash)
    Report
    Hi Howard,

    I guess I have a similar(maybe different) situation:

    I have a form-type process variable FM_1 defined for the workflow WF_1.
    In the custom QPAC I created, I want to access this instance of form(FM_1) associated with WF_1. I'd like to find out the FM_1's structure(field names, data types and corresponding values).

    Can I get this via PATExecutionContext?

    Thanks,
    Scott Jiang
    Compuware Corp.
     
    |
    Mark as:
  • Currently Being Moderated
    3. (Chris_Trubiani),
    Oct 16, 2006 12:52 PM   in reply to (ashwini_dash)
    Report
    Try: PATExecutionContext.getProcessDataValue("/process_data/FM_1");

    Off the top of my head I believe the returned object is of type com.adobe.workflow.task.FormInstance.

    Chris
    Adobe Enterprise Developer Support
     
    |
    Mark as:
  • HowardTreisman
    Currently Being Moderated
    4. HowardTreisman,
    Oct 16, 2006 4:38 PM   in reply to (ashwini_dash)
    Report
    Hi
    Wot Chris sed.
    Except the returned object type is: com.adobe.workflow.datatype.form.FormDataTypeInstanceImpl

    You can call getXFAData() on this object to get the underlying XML for the form. This in turn should allow you to get at the element names and values. It will not tell you the datatypes - these would be determined by your forms xml schema.

    Howard
    http://www.avoka.com
     
    |
    Mark as:
  • Currently Being Moderated
    5. (scott_jiang),
    Oct 17, 2006 1:02 PM   in reply to (ashwini_dash)
    Report
    Thank you both.

    Howard, now I can get this com.adobe.workflow.datatype.form.FormDataTypeInstanceImpl class from adobe-wfk.jar(contained inside LiveCycle.ear). I have further question on this(because I don't think this class is documented anywhere):

    FormDataTypeInstanceImpl.getXFAData() returns a byte[], I can see the runtime form-type structure/value in a xml-like structure using toString() printout. This is exactly what I need. From this point, can you enlighten me on which package I should use to interpret this byte[] array? Any special utility class/method in the SDK can help? Or, I need to write code using DOM/SAX API to traverse the xml tree? Please advise.

    Best regards,
    Scott Jiang
    Compuware Corp.
     
    |
    Mark as:
  • HowardTreisman
    Currently Being Moderated
    6. HowardTreisman,
    Oct 17, 2006 1:14 PM   in reply to (ashwini_dash)
    Report
    Hi Scott
    Once you've got your XML, there are lots of ways you can process it. Usually this mean processing the text using some sort of XML library, such a DOM, JDOM, DOM4J, etc.

    Adobe have some static methods in a class called DOMUtils (or DOMUtil, I can't remember) that has a few simple utility methods, but basically, it ends up with a DOM tree that you can traverse. This is also undocumented, but the methods are fairly self-explanatory.

    Regards,
    Howard
    http://www.avoka.com
     
    |
    Mark as:
  • Currently Being Moderated
    7. (scott_jiang),
    Oct 18, 2006 6:53 AM   in reply to (ashwini_dash)
    Report
    Hi Howard,

    Sounds fair. Further question:

    After I processed some of the node values in xml document, I have to pass in the ***whole updated xml content*** by calling public setXFAData(byte[] xfaData), right? This is the only one I found seems can set value back to workflow.

    Is there better way to do it in Workflow SDK? I am afraid this is going to impact the performance. Please advise.

    Best regards,
    Scott Jiang
    Compuware Corp.
     
    |
    Mark as:
  • Currently Being Moderated
    8. (scott_jiang),
    Oct 18, 2006 10:22 AM   in reply to (ashwini_dash)
    Report
    This is a little weird: I now processed the xml document but setXFAData() doesn't work. I still see the old values from form-type process variable. How can find out what's wrong? There is no error...

    FormDataTypeInstanceImpl.setXFAData(xmlDoc.toString().getBytes());

    Scott
     
    |
    Mark as:
  • Currently Being Moderated
    9. (scott_jiang),
    Oct 18, 2006 11:36 AM   in reply to (ashwini_dash)
    Report
    Never mind. I should use javax.xml.transform.Transformer to convert xml document to String then to byte[]. Now it works.

    transformer.transform(source, output);
    FormDataTypeInstanceImpl.setXFAData(baos.toString().getBytes());

    thank you,
    Scott
     
    |
    Mark as:
  • Currently Being Moderated
    10. (scott_jiang),
    Oct 23, 2006 9:01 AM   in reply to (ashwini_dash)
    Report
    Hi Howard,

    Do you know the default field length output parameter(for String type)?

    I tested my customer QPAC which can take input sql string and set output parameter with a string of multiple record(with delimited for fields and records) but run into the length limitation. This exception is showed in the log when I have a string which length is 105. When I have a smaller string it works.

    which type of data is more suitable for a longer string datatype in SDK?

    2006-10-23 12:54:15,852 ERROR [com.adobe.workflow.AWS] stalling action-instance: 868 with message: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]String or binary data would be truncated.

    thanks!
    Scott
     
    |
    Mark as:
  • Currently Being Moderated
    11. (scott_jiang),
    Oct 23, 2006 10:14 AM   in reply to (ashwini_dash)
    Report
    Just figured out in the Workflow designer, I can change the length of process-level String variable. By default, it is 100...
     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)