北漂，杀杀

ext2中文文档新春版，应用示例，可在MyEclipse下部署实施

dojo教程[中文版]，包括overview

AJAX的DOJO中文文档 AJAX的DOJO中文文档 AJAX的DOJO中文文档

Ant工具 　　Ant是一种基于Java的build工具。理论上来说，它有些类似于（Unix）C中的make ，但没有make的缺陷。目前的最新版本为：Ant 1.8.1。 　　既然我们已经有了make, gnumake, nmake, jam以及其他的build工具为什么还要要一种新的build工具呢？因为Ant的原作者在多种(硬件)平台上开发软件时，无法忍受这些工具的限制和不便。类似于make的工具本质上是基于shell（语言）的：他们计算依赖关系，然后执行命令（这些命令与你在命令行敲的命令没太大区别）。这就意味着你可以很容易地通过使用OS特有的或编写新的（命令）程序扩展该工具；然而，这也意味着你将自己限制在了特定的OS，或特定的OS类型上，如Unix。 　　Makefile也很可恶。任何使用过他们的人都碰到过可恶的tab问题。Ant的原作者经常这样问自己：“是否我的命令不执行只是因为在我的tab前有一个空格？！！”。类似于jam的工具很好地处理了这类问题，但是（用户）必须记住和使用一种新的格式。 　　Ant就不同了。与基于shell命令的扩展模式不同，Ant用Java的类来扩展。（用户）不必编写shell命令，配置文件是基于XML的，通过调用target树，就可执行各种task。每个task由实现了一个实现了特定Task接口的对象来运行。（如果你对Ant一点概念都没有的话，可能看不懂这一节，没有关系，后面会对target,task做详细的介绍。你如果没有太多的时间甚至可以略过这一节，然后再回来浏览一下这里的介绍，那时你就会看懂了。同样，如果你对make之类的工具不熟悉也没关系，下面的介绍根本不会用到make中的概念。） 　　必须承认，这样做，在构造shell命令时会失去一些特有的表达能力。如`find . -name foo -exec rm {}`，但却给了你跨平台的能力－你可以在任何地方工作。如果你真的需要执行一些shell命令，Ant有一个<exec> task，这个task允许执行特定OS上的命令。 Ant的概念 　　当一个代码项目大了以后，每次重新编译，打包，测试等都会变得非常复杂而且重复，因此c语言中有make脚本来帮助这些工作的批量完成。在Java 中应用是平台无关性的，当然不会用平台相关的make脚本来完成这些批处理任务了，ANT本身就是这样一个流程脚本引擎，用于自动化调用程序完成项目的编译，打包，测试等。除了基于JAVA是平台无关的外，脚本的格式是基于XML的，比make脚本来说还要好维护一些。 　　每个ant脚本（缺省叫build.xml）中设置了一系列任务(target)：比如对于一个一般的项目可能需要有以下任务。 　　* 任务1：usage 打印本脚本的帮助信息（缺省） 　　* 任务2：clean <-- init 清空初始化环境 　　* 任务3：javadoc <-- build <-- init 生成JAVADOC 　　* 任务4：jar <-- build <-- init 生成JAR 　　* 任务5：all <-- jar + javadoc <-- build <-- init 完成以上所有任务：jar javadoc 　　而多个任务之间往往又包含了一定了依赖关系：比如把整个应用打包任务(jar)的这个依赖于编译任务(build)，而编译任务又依赖于整个环境初始化任务(init)等。 　　注：我看到很多项目的ant脚本中的命名基本上都是一致的，比如：编译一般叫build或者compile；打包一般叫jar或war；生成文档一般命名为 javadoc或javadocs；执行全部任务all。在每个任务的中，ANT会根据配置调用一些外部应用并配以相应参数执行。虽然ANT可调用的外部应用种类非常丰富，但其实最常用的就2，3个：比如javac javadoc jar等。 Ant与makefile的比较 　　Makefile有一些不足之处，比如很多人都会碰到的烦人的Tab问题。最初的Ant开发者多次强调”只是我在Tab前面加了一个空格，所以我的命令就不能执行”。有一些工具在一定程度上解决了这个问题，但还是有很多其他的问题。Ant则与一般基于命令的工具有所不同，它是Java类的扩展。Ant运行需要的XML格式的文件不是Shell命令文件。它是由一个Project组成的，而一个Project又可分成可多target，target再细分又分成很多task，每一个task都是通过一个实现特定接口的java类来完成的。 　　Ant的优点 　　Ant是Apache软件基金会JAKARTA目录中的一个子项目，它有以下的优点。 　　跨平台性。Ant是纯Java语言编写的，所示具有很好的跨平台性。 　　操作简单。Ant是由一个内置任务和可选任务组成的。Ant运行时需要一个XML文件(构建文件)。 　　Ant通过调用target树，就可以执行各种task。每个task实现了特定接口对象。由于Ant构建文件时XML格式的文件，所以和容易维护和书写，而且结构很清晰。 　　Ant可以集成到开发环境中。由于Ant的跨平台性和操作简单的特点，它很容易集成到一些开发环境中去。

tcpTrace I got fed up with installing Java & Apache SOAP just to get tcpTunnelGUI, so here's a native Win32 version, built using Attila (no MFC :) ). It started out as a copy of the Apache tool, but has taken on a life of its own!. Huh, it does what ? Basically you use it as a tunnel between your client & server. Start tcptrace.exe and up comes a dialog box asking for local port #, destination server, and destination port # (Ignore the logging options for now) . Fill these in, click Ok, and wow are you going to have fun. For example if you are writing a client and testing against a remote server (say www.razorsoft.net ), you can setup Local Port # 8080 Destination Server www.razorsoft.net Destination Port # 80 Now configure your client so that it thinks the server is at localhost:8080. tcpTrace will forward all the traffic from localport:8080 to the remote server (and vica versa), dumping the contents in the process. If you are hosting a server say on port 80 and want to use it, then change your server to run on port 81, and setup Local Port # 80 Destination Server localhost Destination Port # 81 you can now see your incoming traffic. It should work with all the text based IP protocols, I've been using it with SOAP (port 80) & HTTP (port 80), and I know Peter Drayton has been using it with POP3 (port 110) & SMTP (port 25) Command Line Options If you prefer to set-up a tcpTrace session via a command line rather than via the GUI, then there are the following command line options /listen <port> : specifies the local port to listen on. /serverPort <port> : specifies the destination port to forward traffic to. /serverName <servername> : specifies the destination server to forward traffic to. /log <log filename> : enables logging to the specified file. /logFormat <xml | plain> : specifies the logfile format (when logging is enabled) use xml or plain (plain is default). /title <window title> : this overrides the default tcpTrace window title, is useful if you regularly run multiple instances of tcpTrace. /kill : stops all running instances of tcpTrace and exits. this can be useful for batch based testing. e.g. tcptrace /listen 8080 /serverPort 80 /serverName services2.xmethods.net tcptrace /listen 8081 /serverPort 80 /serverName soap.4s4c.com /log c:\log.xml /logFormat xml tcptrace /listen 5049 /serverPort 5049 /serverName nagoya.apache.org /title "Apache Server" If you're doing pure SOAP/HTTP work, you'll want to take a look at proxyTrace as well. My thanks to the following people for helping out Peter Drayton for badgering me into writing the logging support. Matt Humphrey for spotting and fixing a problem with large payloads and the socket shutdown sequence. Steve Witham for fixing my terrible docs, any errors are of course still mine. Everyone who made suggestions for new features. Release History v0.8.1 (Build 717) May 28, 2005 Can now enter upto 500 characters for the server name. v0.8.0 (Build 712) December 17, 2003 If it can't listen on the specified local port it reports an error instead of silently failing. v0.7.3 (Build 710) December 28, 2002 Trace settings are now reflected in the window title when /title hasn't been used. Thanks to Tomas Restrepo for the suggestion. v0.7.2 (Build 708) December 28, 2002 Added option to fix-up single \r & \n into windows linefeeds so that the display stays formated when tracing against non-windows applications. v0.7.1 (Build 683) December 18, 2002 Added "Show Nulls" option, so that data past a NULL character can be seen. v0.7.0 (Build 669) July 6, 2002 Can now select separate fonts for the list view and the text windows. word wrap setting now remembered across invocations. bug with word wrap toggle loosing font setting fixed. v0.6.0 (Build 648) March 27, 2002 [aka the Conference Presenters Edition!] Font selection is now remembered across invocations. The /title command line option added to override the standard window title, useful if you have lots of instances running at the same time. Connections that were still active when the trace is stopped, now have their data flushed to the log file. A problem with line endings in the XML log was fixed. v0.5.0 (Build 626) September 2, 2001 Added support for changing the display font. Fixed the problems with clear. The payload views for the active connection are now dynamically updated. v0.4.0 (Build 521) February 21, 2001 Added support to log the trace info to a file either in plain text or XML format. Added support for starting / stopping / logging from the command line (via Chris Sells's excellent command line parser). Added a stop trace feature v0.3.0 (Build 234) January 15, 2001 Matt Humphrey fixed a problem with large payloads getting truncated / dropped bytes Matt Humphrey fixed a problem with the socket shutdown sequnce Matt Humphrey added support for the up and down cursor keys to work on the connection list Added word wrap support for the request / response windows v0.2.1 (Build 122) December 1, 2000 Corrected the tab order on the trace settings dialog v0.2.0 (Build 120) September 30, 2000 The last used Trace settings are now remembered for next time Trace dialog box initially pops up Legal gunk added to about dialog box Updated docs with additions from Steve Witham Added copy of these docs to the download v0.1.0 (Build 92) September 12, 2000 Initial Release

基于J2EE的Ajax应用，帮助程序开发，更好的展现业务。教程为pdf文件。

讲述Ajax的原理，并提供源代码。教程以pdf形式提供。

hibernate3.2中文开发手册