decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Wrong in so many ways | 451 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Grails also is built on top of and uses the standard Java class libraries
Authored by: bugstomper on Thursday, May 03 2012 @ 11:20 PM EDT
Nope, Grails may have been acquired by SpringSource, but it is still a framework that is built on top of the standard Java Platform, which includes the standard class libraries.

From the wikipedia article you linked to

Integration with the Java platform

Grails is built on top of and is part of the Java platform meaning it's very easy to integrate with Java libraries, frameworks and existing code bases. The most prominent feature Grails offers in this area is the transparent integration of classes which are mapped with the Hibernate ORM framework. This means existing applications which use Hibernate can use Grails without recompiling the code or reconfiguring the Hibernate classes while using the dynamic persistence methods discussed above. [3]

One consequence of this is that scaffolding can be configured for Java classes mapped with Hibernate. Another consequence is that the capabilities of the Grails web framework are fully available for these classes and the applications which use them.

That is not an example of classes which replace the standard class libraries to provide equivalent functionality while having different package and class organization for a different SSO. Grails assumes the standard libraries exist and it uses them, not replaces them.

[ Reply to This | Parent | # ]

Wrong in so many ways
Authored by: jbb on Thursday, May 03 2012 @ 11:32 PM EDT
First, Groovy is not the Java language. If you are going to open it up to different languages then you will find that the vast majority don't use Java APIs. Second, Even though Groovy is a different language, it still uses the core Java APIs. Finally, the Grails framework is built on top of the Groovy language and on top of the core Java APIs. It doesn't replace them. This is just like the Java Spring framework (that we think Ellison was referring to). It too is a framework that is built on top of the core APIs.

People either build on top of the core APIs (Spring, Grails) or they re-implement them: Android, Harmony, OpenJDK, GNU Classpath. No one is creates a completely incompatible re-implementation. This makes it much easier for things to inter-operate. For example since Groovy uses the core Java APIs and since Android re-implements the core Java APIs, you should be able to port Groovy to Android without too much work. If Google used an entirely different API, like Oracle is demanding, then such ports become either very difficult or impossible.

So if you want to see what the core APIs are really are then look inside of Spring and look inside of Groovy and Grails. See what APIs they depend on. If Oracle gets a monopoly on these core Java APIs then they will also have a monopoly on the many third-party frameworks such as Spring and Groovy and Grails.

---
Our job is to remind ourselves that there are more contexts than the one we’re in now — the one that we think is reality.
-- Alan Kay

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )