Project最主要是要解决三个斚w的问?
1.用什么Software来生成可交互的Form?
2.用什么Open source tools来Pre-fill Form?
3.在User填完Data?又以什么方式Submit 到Server处理?
对于W一个问?自然是用Adobe 的Software?但是用Acrobat Proq是用Lifecycle Designer, 却让我费了不劲.Z么咧?因ؓAcrobat Pro和Lifecycle Designer 处理的Form的格式是不一L(fng). Acrobat Pro里面用的是AcroForm,是Acrobat3.0开始用的格?而Lifecycle Designer里面用的是Xfa Form,是基于XML? 两者的不同请参考以下的摘录:
The interactive forms that you create in LiveCycle Designer are different than the interactive forms that you create in Adobe Acrobat. If you create an interactive form in Acrobat, your form is based on Adobe’s Acroform technology. This technology dates back to Acrobat version 3, and Adobe provides the “Acrobat Forms API Reference” to provide the technical details for this technology. I would not recommend using Acroform technology because XFA is the better technology.
If you are moving from Acroforms to XFA forms, you need to know a couple of important facts about these two technologies:
1.LiveCycle Designer can edit a PDF form created in Acrobat, but Acrobat cannot edit a PDF form created in Designer.
2.JavaScript works differently in these two technologies. Some of the JavaScript routines that work in Acroforms will not work in XFA forms. Adobe has documented these differences in a 43 page online PDF called, “Converting Acrobat JavaScript for Use in LiveCycle Designer Forms.” Designer is a much more robust tool for using JavaScript in your forms, so I recommend that you learn how to script with the XFA object model. See Chapter 4, “Form Scripting,” for more information.
PS: you can find more in the below link: More info about XFA
Lifecycle designer 是后来才有的东西,自然是比Acrobat Pro更先q也更适合用于交互,但我的项目最l还是选了Acrobat Pro,因ؓ我的W二个问题的{案是iText. iText可以用来Pre-fill XFA格式的Form,但是不知道ؓ什么用iText Create的submit button不能submit XFA form(按了Button后没有反?,后来上网查到原来iText不支持XFA Form, 所以也只能用Acrobat?
而且用Acrobat Pro创徏的Form有两个我自己觉得不错的优?以TextFeildcdZ?:
1. Acrobat Pro创徏的AcroForm是没有层ơ结构的,而LifeCycle Desinger创徏的Form是有层次?什么意思咧?举个例子,同样是Add一个TextFeild, 把它命名为CustomerName,在AcroForm里面的名字就是CustomerName?而在XFA Form里面成了topmostSubForm[0].Page1[0].CustomerName[0],咋一?q真是烦.而且你的PDF一改的?那你的Feild name也相应改?q样Program也要改了....
2. Acrobat Pro创徏的AcroForm的TextFeild可以自适应大小,一个TextFeildL有一定的长度,但要填的Value׃知有多长?有可能有个CustomerName真的很长?q在XFA Form里面׃有些Value Show不出?但Acrobat Pro创徏的AcroForm的TextFeild可以根据Value的大而改变字体的大小来适应TextFeild的长?
以上两点是我自己的认?也许Lifecycle Designer也可以做C上的效果,但目前我是不?因ؓ接触Lifecycle Designer比较?yu)?如果有大虄道的话请多多指教.
]]>
The problem is that there is a limit on the size of a compiled method in a
Java class file, and that limit is what we're running up against. Recall
that a JSP page is compiled into a servlet, and into essentially only one
method in that servlet. Hence, if your page contains many, many tags, that
method becomes too big, and up comes the exception that you're seeing.
There are a couple of (partial) solutions.
1) Break your giant page up into multiple smaller pages and bring them
together at run time using <jsp:include>. Note that <%@include> won't work,
because that's a compile-time include, which will get you straight back to
the original problem.
2) Look for places to save on tags. For example, the <html:option> tag was
recently extended to allow the specification of the text to display, so
that you can replace this:
<html:option ... ><bean:message key="foo"/></html:option>
with this:
<html:option ... key="foo"/>
More info pls access this link: Solution
我就是用了第一U方法解决的,之前include JSP的时候用?a href="mailto:%@include">%@include, 后来用了<jsp:include>׃会用问题?Z贴一下两者的区别:
后记:|上q有一USolution:
try giving this in the deployment descriptor.
<jsp-param>
<param-name>noTryBlocks</param-name>
<param-value>true</param-value>
</jsp-param>
本h没有试过, 不知好不好用....
]]>