background preloader

Project Lombok

Project Lombok

The Scala Programming Language jsdt - Debug javascript in ie,firefox,chrome,safari,opera and all browsers support ajax Javascript Debug Toolkit is a software can debug javascript in ie,firefox,safari,chrome,opera,mobile ie browser,mobile opera browser and so on .It works in all the browser support ajax. Javascript Debug Toolkit 2.2.0 is published! update site URL: Browser support of debug tools There are tow version of jsdt. Javascript Debug Toolkit s0.5 is a Green-free installation software. *document* Green version of jsdt,need JRE1.5 *download* Install version in windows. Javascript Debug Toolkit 2.2.0 version is a eclipse plugin to debug javascript crossbrowser. *document* *download* Javascript Debug Toolkit 可以在ie,firefox,safari,chrome,opera, 移动IE浏览器,移动opera浏览器等任何支持ajax的浏览器中调试javascript. jsdt有两个版本 独立版是绿色跨平台跨浏览器的软件,可以在windows和linux上运行 文档 解压版需要安装jre1.5 解压版 安装版在windows下安装即可运行 *安装版*

Stereotype Annotations Cut Down XML Configuration in Spring nnotations have been part of the Spring Model-View-Controller (MVC) Framework since Spring 2.0. In Spring, annotations can greatly reduce the amount of XML bean configuration and wiring needed. Given the many components of the Spring MVC environment (handler mapping, controller, view resolver, and view), XML configuration can turn unwieldy in a hurry. So, Spring MVC configuration is certainly one area that can really benefit from reduced configuration. As of Spring 2.5, the framework added new annotations to more easily configure and assemble the components of a multi-layered application, such as you might find in an MVC-designed system. In fact, an important type of annotation added in Spring 2.5, stereotype annotations, is for configuring the Spring MVC controller components. Are these new annotations critical to your applications? In Spring framework 3.0 there will be a number of deprecations, for example, the old MVC controller hierarchy. Stereotype Annotations

Fantom Programming Language On TermKit I've been administering Unix machines for many years now, and frankly, it kinda sucks. It makes me wonder, when sitting in front of a crisp, 2.3 million pixel display (i.e. a laptop) why I'm telling those pixels to draw me a computer terminal from the 80s. And yet, that's what us tech nerds do every day. The default Unix toolchain, marked in time by the 1970 epoch, operates in a world where data is either binary or text, and text is displayed in monospace chunks. The Unix philosophy talks about software as a toolset, about tiny programs that can be composed seamlessly. In the meantime, we've gotten a lot better at displaying information. And yet the world of Unix is rife with jargon, invisible processes, traps and legacy bits. So while I agree that having a flexible toolbox is great, in my opinion, those pieces could be built a lot better. I see TermKit as an extension of what Apple did with OS X, in particular the system tools like Disk Utility and Activity Monitor. Rich Display Pipes

Annotation based Caching in Java I probably had to write cache to store results of expensive operations or queries a dozens of times over last ten years of Java. And this week, I had to redo again. Though, there are a lot of libraries such as JCS , Terracota or Tangosol, but I just decided to write a simple implementation myself. First I defined an annotation that will be used to mark any class or methods cachable: 1 import java.lang.reflect.*; 2 import java.lang.annotation.*; 3 4 5 6 7 8 9 @Target({ElementType.TYPE, ElementType.METHOD}) 10 @Retention(RetentionPolicy.RUNTIME) 11 public @interface Cacheable { 12 13 14 15 boolean cache() default true; 1617 18 19 20 21 22 int maxCapacity() default 1000; 2324 25 26 27 28 boolean synchronizeAccess() default false; 2930 int timeoutInSecs() default 300; 3132 33 34 35 public boolean canReloadAsynchronously() default false; 36 } 3738 I then defined a map class to store cache: A couple of interfaces to load or search key/values: A utility class for storing pair of objects:

Online Fantom Playground untitled Annotation-Based Transactions in Spring - Wheeler Software I n this article, I'm going to show you how to use transaction management annotations in Spring. I'm using Spring 2.5 though these features have been available at least since Spring 2.0. Spring provides several different approaches to transaction management: Programmatic: You can write your transactions using Java source code directly. Declarative: You can declare transaction definitions in either a centralized way using XML or in a distributed way using annotations: XML-based: You can configure transactions in Spring's centralized application context file. Proxy-based: In this approach you wrap your service beans with transactional proxies. AOP-based: Here you define AOP aspects to endow your service beans with transactional semantics. Annotation-based: You can use Java 5 annotations to distribute transaction configuration across Java classes. As the title suggests, this article deals with annotation-based configuration.

Getting Started Database setup with DBTestCase subclass Step 2: Extend the DBTestCase class Now you need to create a test class. One way to use Dbunit is to have the test class extend the DBTestCase class. You may also use a subclasses of DBTestCase, such as one of these: The following is a sample implementation that returns a connection to a Hypersonic database and a xml dataset: Alternatively, PrepAndExpectedTestCase: (see the class JavaDoc) TODO add example here Step 3: (Optional) Implement getSetUpOperation() and getTearDownOperation() methods By default, Dbunit performs a CLEAN_INSERT operation before executing each test and performs no cleanup operation afterward. The following example demonstrates how you can easily override the operation executed before or after your test. Step 4: (Optional) Override method setUpDatabaseConfig(DatabaseConfig config) Use this to change some configuration settings of the dbunit DatabaseConfig. The following example demonstrates how you can easily override this method:

125-piece metal puzzle can be put together to form a working gun This might look like a relatively straightforward 3D metal puzzle, but it holds a secret: if you put some of its pieces together in the right way, it'll turn into a functioning gun. Yes, if you take about 20 of the pieces in this 125-piece puzzle and put them together properly, you'll have a fully-functional single-shot .45 caliber handgun. Uh, cool? Luckily, the whole thing requires a special key to begin disassembling it, so the chances of some kid stumbling upon it at a toy store and ending up with a deadly weapon are slim to none. Maxton via Neatorama

A Practical Guide to Using an Aspect Library (part I) « What's on your bookshelf? | Main | Tips for using Eclipse effectively » February 20, 2006 A Practical Guide to Using an Aspect Library (part I) This entry represents part one of a two-part guide to using an aspect library (with AspectJ). I wrote it in December of last year, and have been waiting to finish part II before publishing it. Introduction With the arrival of AspectJ 5 and the Spring 2.0 milestone builds, many of you will be working with AspectJ-based aspect libraries for the first time. I'm assuming that for the time being you don't want to write your own aspects: you just want to use the capabilities of an existing library. The library supports an @Configurable annotation. @Configurable public class Account {...} When the annotation is used like this without a value, an instance of Account will be dependency injected by Spring, using the fully-qualifed class name of Account as the bean name. @Configurable("accountBean") public class Account {...} Introducing Load-time Weaving

System.Data.SQLite: System.Data.SQLite Download Page Build Product Names Beginning with System.Data.SQLite version (, the following templates will be used for the names of the build products: sqlite-netFx-source-version.tar.gz sqlite-framework-setup-cpu-year-version.exe sqlite-framework-setup-bundle-cpu-year-version.exe System.Data.SQLite.version.nupkg System.Data.SQLite.variant.version.nupkg Templates (1) and (2) are used for source-code packages. Template (1) is used for generic source-code packages and template (2) is used for source-code packages that are generally only useful on unix-like platforms. Template (3) is used for the setup package. The cpu in templates (3) and (4) will be one of x86, x64, arm, ia64. Canonical Source Code