Terry's Blog

Because some scripts may take an excessive amount of time to run, Internet Explorer prompts the user to decide whether they would like to continue running the slow script. Some tests and benchmarks may use scripts that take a long time to run and may want to increase the amount of time before the message box appears. In Internet Explorer, the script time-out value can be changed on specific client machines by modifying a registry entry. To change this time-out value in Internet Explorer 4.0, 5.0, 6, 7, or 8, follow these steps: Using a Registry Editor such as Regedt32.exe, open this key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles Note If the Styles key is not present, create a new key that is called Styles. Create a new DWORD value called "MaxScriptStatements" under this key and set the value to the desired number of script statements. If you are unsure of what value you need to set this to, you can set it to a DWORD value of 0xFFFFFFFF to completely avoid...

This is the problem caused by MS office 2007 pointer pointed to non-existing DLL. Solution: Start Regedit and goto the following key: HKEY_CURRENT_USER\Software\Microsoft\Shared Tools\Proofing Tools\1.0\Override\en-US I had 2 entries (DLL and LEX) pointing to non-existing files. Rename these to oldDLL and oldLEX. After this change all Spell Checking worked normal again.

Starting from iText 2.0.0 you need the BouncyCastle.jars as soon as you use encryption. http://www.bouncycastle.org/latest_releases.html http://sourceforge.net/projects/itext/files/extrajars/

Must use the size attribute of the input element of HTML in order to prevent "/" appear on the input box when displaying the value from jsp variable. For example, <input type="text" name="path" value=""<%=path%>" size="80">

Javascript刷新頁面的幾種方法： 1 history.go(0) 1 history.go(0) 2 location.reload() 3 location=location 4 location.assign(location) 5 document.execCommand('Refresh') 6 window.navigate(location) 7 location.replace(location) 8 document.URL=location.href

Manifest.mf Extension-Name: xx.app.audit.als Specification-Version: 1.0.1 Implementation-Version: 1.0.1 Specification-Title: xx.app.audit.als Implementation-Title: xx.app.audit.als Implementation-Vendor: xxx Extension-List: log4j log4j-Extension-Name: apache.log4j log4j-Specification-Version: 1.2.15 log4j-Implementation-Version: 1.2.15 P.S.: remember return should be provided for the last line

Keep in mind these best practices when developing shared Java EE libraries and optional packages: Use shared Java EE Libraries when you want to share one or more Java EE modules (EJBs, Web Applications, Enterprise Applications, or plain Java classes) with multiple Enterprise Applications. If you need to deploy a standalone Java EE module, such as an EJB JAR file, as a shared Java EE library, package the module within an Enterprise Application. Doing so avoids potential URI conflicts, because the library URI of a standalone module is derived from the deployment name. If you choose to deploy a shared Java EE library as a standalone Java EE module, always specify a known deployment name during deployment and use that name as the URI in referencing applications. Use optional packages when multiple Java EE archive files need to share a set of Java classes. If you have a set of classes that must be available to applications in an entire domain, and you do not frequently upda...