Strange.The first shot is shows the doc1 mapping.  The second shows the waterlogo mapping.   Both variables are of type "document"I've also attached the DDX file so you can see how the mappings fit into the PDF source attributes

huh, weird.  I don't have that file in my temp.Try this one:

I've attached a sample

1 - The supported platform matrix is included in the LiveCycle documentation:  http://help.adobe.com/en_US/LiveCycle/9.5/supported_platforms.htmlVista 32 and 64 are supported for turnkey (JBoss) for evaluation and development only.2 -  Yes, you still need a 32 bit JVM3 - You can do it, but that comb...

The source attribute can be thought of as a reference id rather than the file name.  You can load the image into a document object and then use the invokeDDX operation to map the image document to the source attribute.

Yes, Generator is a module that runs in the LiveCycle framework.  When you purchase Generator, you get the LiveCycle framework as part of the purchase.

The Source reference can be considered an identifier instead of an actual file name.   You would read the image file into a Document variable and then use the InvokeDDX property sheet to map the document variable into the specified source entry.

http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/000064.htmlhttp://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/000044.html

If you are talking about extracting data from a PDF form then you can do that with Forms.processFormSubmission or FormDataIntegration.exportData

Java based web services will work fine (as will ones created in other languages), and I find the Eclipse JBoss Tools pretty easy to use.  If you are using the LiveCycle ES server products, you can create a workflow and expose that using a web service end point as well.Since you are building the WS f...