Last changed Jul 20, 2008 13:25 by Helmut Hauschild
Portal für Pflege, a new Grails based German healthcare placement portal, started it's open beta test in July (betatest.portalfuerpflege.de). If everything goes well, the portal will be fully operational in October. An English version will follow later.
Last changed May 19, 2008 07:47 by Sergey Nebolsin
After a long way we finally released 0.3 version of the Grails Quartz plugin (and as of a blocker bug in this release, 0.3.1 arrived in several hours).
In this release we primarily focused on plugin's configuration and flexibility as well as on fixing issues. Here's the list of implemented features:
- upgraded to Quartz 1.6.0
- plugin's configuration using 'grails-app/conf/QuartzConfig. …
Labels
(None)
Comments (10)
Apr 19, 2006
E.Nielsen says:
If it just wasn't that Grails is a much cooler name... you probably just should ...If it just wasn't that Grails is a much cooler name... you probably just should have replied with this image :-D
Apr 19, 2006
graeme says:
hmmm, yes rather amusing :).. well its no big deal really.. i prefer just grails...hmmm, yes rather amusing
.. well its no big deal really.. i prefer just grails anyway. If you don't mind I will probably delete your comment as this is a ..ahem.. "family" site and we don't condone such references to foul language 
May 15, 2006
tom latka says:
I' ve heard, oracle is supporting grails, great\!I' ve heard, oracle is supporting grails, great!
http://www.infoworld.com/article/06/05/11/78223_Hnoraclejavaone_1.html
"[Oracle] will also announce intentions to contribute engineering resources to the open source Grails proje
ct."
Jul 20, 2006
zjg_robin says:
Hi, everyone I downloaded 0.2 and use it created a proj...Hi, everyone
I downloaded 0.2 and use it created a project, just a very simple test, one domain class, but when I use the command "grails run-app" to start it , an exception raised as below:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.codehause.groovy.grails.orm.hibernate.support.HibernateDialectDetectorFactoryBean#114d18f' defined in resource loaded through InputStream: Initialization of bean failed; nest exception is org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is Java.sql.SQLException: unsupported features
how to do with it?
Thanks, Robin
Jul 20, 2006
graeme says:
Hi Robin, Your database doesn't support autodetection of the Hibernate dialect ...Hi Robin,
Your database doesn't support auto-detection of the Hibernate dialect so you would need to set it explicity for whichever product you are using (see http://grails.org/Configuration for details) on setting a custom dialect.
In future could you post questions like this to the mailing list (see http://grails.org/Mailing+lists) ? You are likely to get a quicker response and the wiki is not really the place for such questions.. thanks!!
Graeme
Jul 20, 2006
zjg_robin says:
Hi Graeme, Thank you for your answer, it works, but another problem...Hi Graeme,
Thank you for your answer, it works, but another problem occurs. I have a table which has a column named id, but the id is not a Long type, it is a String and editable as other columns, how to implement this? In Grails domain class, the id is fixed as Long type and can not be edit.
Thanks. Robin
Mar 30
Eric Wilson says:
Hi Graeme, Since I believe you have an open mind about Groovy and at least some ...Hi Graeme,
Since I believe you have an open mind about Groovy and at least some voice about it, I direct this suggestion to you. Groovy has to find a way to catch more errors at compile time. A programmer can type junk into a Groovy class and the compiler will not catch it, if it could possibly be a method call or a field that magically appears at runtime. Here is one suggestion. Define a keyword, such as "nonDynamic". If a programmer writes a class that should not have any fields or methods added at runtime, then they could use the keyword, such as
nonDynamic class Foo {
}
Then the compiler, seeing the "nonDynamic" keyword would flag any reference to a nonexistent method in class Foo as a compile error.
Hopefully we can find a way to get the benefits of a dynamic languange without drawbacks. Thanks.
Eric
May 15
Bar says:
I would like to use groovy and grails to implement a service . I would need a fi...I would like to use groovy and grails to implement a service . I would need a final service jar to use it along with my existing application. How do we do that ? Grails only currently allows only to build a war. Will I be able to get my specific service component and it dependents from this war? Pls explain
thanks
bar
Jun 20
Nick Verlinde says:
"Groovy has to find a way to catch more errors at compile time. A programm..."Groovy has to find a way to catch more errors at compile time. A programmer can type junk into a Groovy class and the compiler will not catch it, Here is one suggestion. Define a keyword, such as "nonDynamic" - Eric Wilson
this feature currently exists, just change your class file extension to .java
Jun 23
Matthew Lachman says:
"this feature currently exists, just change your class file extension to .java" ..."this feature currently exists, just change your class file extension to .java"
I'm sorry, but if I have to go to .java then it's not a feature it's a bug. Not to mention the fact that there is syntax that is perfectly legal in Groovy that Java would complain about.