Hello,<br /><br />We have a forms processing engine running on Windows 200K/XP using Java and jboss' app. server. I am currently having trouble getting XDP functioning properly and I am wondering if someone out there can help. Here are the steps:<br /><br />Using LifeCycle Designer 7.0 I create a form. This form basically has a Submit button and 1 text field. I save this form in both XDP and PDF. The submit button has a submit event in the XDP. <br /><br />Before I attempt to render this to Reader, I modify the XDP to change the 'target' attribute of the <submit> element and I also add a value to the text field. I also add (at the end of the XDP) the PDF file (Base64 encoded) as a <pdf> element. Basically the end of the pdf looks like this:<br /><br /><pdf xmlns="http://ns.adobe.com/xdp/pdf/"><br /> <document><?KeepOnDisk?><br /> <chunk>Base64EncodedStuff<br /> </chunk><br /> </document><br /></pdf><br /></xdp:xdp><br /><br />Once this is done I stream it down to the browser (IE 6.0) and the form comes up in Reader. What I notice is this.<br /><br />1.) Even though the text field (in the xdp) has a value, it doesn't display.<br /><br />2.) Even though the submit button's submit event is setup to call my servlet (in the xdp), it doesn't submit.<br /><br />What I have observed is that what ever I did to the form when the PDF was generated, that's the behavior I see. If I define the submit URL to be 'test.jsp' during form design time, when rendered, the form attempts to find test.jsp instead of the url I defined in the XDP. This is true for the field value as well. It will onlt display the default value as designed into the form.<br /><br />What am I missing? I thought the whole purpose of XDP was to facilitate this exact type of processing! Does the PDF override everything in the XDP?<br /><br />All help is greatly appreciated.<br /><br />Thanks,<br />Bob<br /><br />P.S. And this could be important...If I have a form with ONLY a submit button, I can get it to call my servlet. Very, very strange!