Java J2EE Portal
Enterprise Java Station
J2EE curve
Java News / Articles
Java News / Articles
A quick look at EJB 3.0 Stateless Session Beans
web2
Enterprise 2.0: Bringing Web2.0 Collaboration and Social networking to Ente
Java Cryptography : A Bird's Eye View
Processing...
Buy Java, Deals On Software Technology Store
Click here for great deals on computers, laptops, software and books
Groovy releases new and improved version - JSR 06 PDF Print
Written by Content Team   
Jul 06, 2006 at 04:45 AM

Groovy has released version JSR 06, which is expected to be the last release before the release candidates. With Groovy now close to version 1.0, JSR 06 should have most if not all the features of 1.0.

The Groovy website as yet doesn't have a news item on JSR 06, but JSR 06 is very much available for download at http://dist.codehaus.org/groovy/distributions/. Apart from bug fixes, this release also provides various improvements and additions. Key amongst those are:

1) @Property Syntax has been removed. This change will have a significant impact on existing Groovy code. Refer to @Property proposal
2) Provide Mock support with pure Groovy. No external mock library needed any longer. Refer to Groovy 1246
3) Full stored procedure support for groovy.sql.Sql. Refer to Groovy 493

Groovy project lead Guillaume Laforge in a recent interview said that "Groovy somehow bridges two worlds: the scripting world and the enterprise Java world" and that the main target audience for Groovy is the Java developer crowd. For more info on Groovy and its relevance to Java developers, do check out this Groovy interview.

Reference:
>> Groovy Release Notes

Related:
>> Oracle backs Groovy and Grails
>> Groovy bridges the scripting and the enterprise Java worlds
>> Scripting Jython and Groovy using Coyote with NetBeans
>> Jython vs Groovy


User Comments

Comment by Guillaume Laforge on 2006-07-12 00:36:20
Groovy won't fully support annotations before 1.x or 2.0. And this @Property annotation was verbose and somewhat foreign to the rest of the language. So instead of it, we prefer a less verbose and simpler convention for defining properties (private fields with getter and setter), rather than a half-backed pseudo hard-coded annotation. This annotation was first introduced when the idea of AST (Abstract Syntax Tree) macros emerged, but which hasn't been implemented so far, if ever.

Comment by 'Guest' on 2006-07-06 07:34:46
What were the reasons for @Property to be inserted and then removed from Groovy? It seems logical to mark a variable as a property if it was being used as one. 
Your Name / Email Address
Comment
Spam Protection - Please enter the code in the image -

Listen to code


Add This Feed Button

Enter your Email


Java Expert Interviews
GraemeRocher-Grails
Grails is a breath of fresh air for Java developers
Open-Source keeps me 'coding fit'
Jesper_Joergensen
WebLogic 9.0 takes J2EE to a new level of reliability and scalability
Processing...
Go to top of page  Home |
SiteMap

Copyright 2004 to 2008 Rightrix Solutions. All rights reserved. All product names are trademarks of their respective companies. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Rightrix Solutions and IndicThreads.com are independent of Sun Microsystems, Inc.

Views expressed at IndicThreads.com reflect the views of the authors alone, and do not necessarily reflect those of IndicThreads.com. IndicThreads.com and it's authors are not responsible for reader comments and opinions.

Enterprise Java J2EE JEE Portal >> IndicThreads.com