Apple Developer. An Objective-C Tutorial for J2EE Dev. Scala. Specs2 @ GitHub. Specify your software using both text and Scala code class HelloWorldSpec extends Specification { def is = s2""" This is a specification for the 'Hello world' string The 'Hello world' string should contain 11 characters $e1 start with 'Hello' $e2 end with 'world' $e3 """ def e1 = "Hello world" must haveSize(11) def e2 = "Hello world" must startWith("Hello") def e3 = "Hello world" must endWith("world") } Use different styles of specifications /** This is the "Unit" style for specifications */class HelloWorldSpec extends Specification { "This is a specification for the 'Hello world' string".txt "The 'Hello world' string should" >> { "contain 11 characters" >> { "Hello world" must haveSize(11) } "start with 'Hello'" >> { "Hello world" must startWith("Hello") } "end with 'world'" >> { "Hello world" must endWith("world") } }} Document your APIs with compiler-checked examples Manage contexts for integration testing.
Scalacheck. Functional programming. Scala Review. Posted by jeffvroom in All, Java/JEE, Software. Trackback Scala is an impressive language built on top of the Java runtime. Many of the irksome problems in Java have been fixed in Scala. I like: * The language is concise and eliminates unecessary semicolons, type definitions and braces. For simple programs, the code is clean and easy to read. * Scala classes can use and extend Java classes and can be made to work the other way around though a bit awkward in some areas. * More flexible imports including a way to rename a class on import * Addition of an “object” keyword so you can define static instances more flexibly (this replaces static members) * Improved flexibility of get/set methods, properties and fields * Interfaces replaced by more flexible Traits which do a better job approximating multiple inheritance * More flexible abstract definitions A few other Java changes are maybe good or bad: * == In scala means .equals in java and “eq” in scala means ==.
Like this: Like Loading... Android. Spring Android. Java. Spring Source. Framework API. Reference Doc. Java Persistence API. Hibernate. JPA 2 Annotations - The Complete Reference (JavaDoc) Fast Object Database for Java - with JPA/JDO support ObjectDB ObjectDB Home » JPA » Annotations JPA Reference Which JPA is Faster? See a comparison of Hibernate, EclipseLink, OpenJPA, DataNucleus, MySQL, PostgreSQL, Derby, HSQLDB, DB4O by Versant, H2 Database, SQLite and ObjectDB in the JPA Benchmark.
JPA 2 Annotations JPA defines dozens of annotations that can be divided into the following groups: Annotations for JPA aware classes: Annotations for fields in JPA persistable classes: Annotations for additional JPA configuration: Annotations for JPA lifecycle event callbacks: JPA Annotations for Callback Methods Java EE container annotations: JPA Annotations for Java EE Many other JPA annotations are designated for Object Relational Mapping (ORM) JPA providers (for mapping between a relational database and an object model and for direct SQL queries): These ORM annotations are silently ignored by ObjectDB.
Java Performance Tuning.