User grails create-domain-class com. All model classes come with have a version and id property of type Long and a toString method by default. Dynamic Scaffolding Grails supports dynamic and static scaffolding for the user interface. To use dynamic scaffolding, create controllers for your domain class via the following commands:.
Feedback grails generate-controller com. User grails generate-controller com. Do this also for UserController and CommentController. Testing the generated application Run the application again via:. Exercise: Bootstrap and persists data 6. Target In this exercise you create example data and store the data between application restarts.
Bootstrapping example data Grails allows to simulate example data this is called bootstrapping. Store the data By default, the data maintained in the web application is not stored. Remove the bootstrapped entries as you will otherwise get errors as the system tries to create the same entries again. Static scaffolding To switch from dynamic scaffolding to static scaffolding, you need to have views.
Type in the following to create a scaffold for the controller and the view. Feedback grails generate-views com. User grails generate-views com. The JDK is required for this step. Change the layout of your Grails application 7. Changing the generated views If you are not satisfied with the order of the fields, you can change the views directly.
Create a WAR archive Type the following command to create a war archive. Testing your application The command create-domain-class automatically creates a test for the domain-class. Using Eclipse for Grails development The following requires that Eclipse is installed with the Groovy plug-in. At least for me the configuration dialog showed an error.
I did ignore this error and the re-compiled project did not show errors. Grails links List of Grails tutorials. Groovy tutorials. List of Grails tutorials. See License for license information. Grails platform takes care of the infrastructure and dependencies to run a web app such that the developers can concentrate on building the functionalities for the product. Grails -a great framework for the startup organizations to launch the product from the development mode to production mode.
How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. What are "Groovy" and "Grails" and what kinds of applications are built using them? Ask Question. Asked 12 years, 1 month ago. Active 2 years, 10 months ago. Viewed 83k times. What is Grails?
What kind of applications are built using Groovy on Grails? Improve this question. Ken Liu Rachel Rachel Also, it's just Grails. Not Groovy on Grails that makes no sense.. You're lucky Marc Palmer hasn't seen this question : — leebutts. It's just Grails. Yes, 5 years ago in the Ruby on Rails guys complained and the framework that was called 'Groovy on Rails' was renamed to just Grails. Java has an ecosystem that has matured through years of development, establishing it as one of the most reliable platforms out there.
Yet it lacks the means necessary to get the job done quickly, especially for things like web applications. In an attempt to avoid frustrations with these types of issues, developers often opt instead for implementation languages and their modern web frameworks, such as Ruby with Ruby on Rails, Python with Django, and so on.
Unlike Java, these provide a much more streamlined path to building a web application. Fortunately, for Java developers wanting to build web applications, there is a better way, and it involves Grails. We will look at some examples where Grails is appealing to us as Java developers and might tempt someone else to give it a shot as well.
In a startup I worked for, we had this exact problem. We had a Spring application which was becoming a pain to work with.
With it growing larger and larger, we soon found that refactoring and adding functionality was taking us way longer than it should. Combining that with some other motivations led us to decide to rewrite our core application.
We were also open to changing or replacing existing technology stack. Grails looked like a viable choice since it runs in the JVM and is built on top of technologies we already knew. It uses the Groovy programming language but at the same time allows you to mix it with Java.
So we took the plunge. One thing Grails really excels at is making it easy to start a new project. It is as simple as running a command which creates the project structure with all the folders needed for the classes you will add later.
Adding model classes, controllers, services and web pages takes a similarly minimal amount of effort. The only thing you need to take care of is naming and placing stuff correctly. Unlike Java, there is virtually no boilerplate code that needs to be there just because it needs to be. This is partially made possible by using Spring and Hibernate which are two of the pillars of Grails, as well as the concept of coding by convention.
To run the project, Grails comes bundled with Apache Tomcat as a development server. All we have to do is run the project in our IDE and the server will be fired up with our code deployed. To use an existing database, we need to configure the JDBC connection properties or just leave it by default to use an in-memory instance. Once the server with Grails is running takes a little bit more than a Spring MVC application , we can modify the code and the hot deploy functionality will keep our debug session equipped with the latest version.
The only classes that cannot get reloaded this way are the entity classes. The efficiency and precision of Grails code means faster development with fewer bugs and less code. Iterative development is a hallmark of the Grails framework because teams can carve out functionality in short sprints, with checkpoints and testing along the way.
The Grails plugin system enables code reuse across projects, allowing development teams to spend less time solving common web problems and more time implementing real business requirements. Low Maintenance. Foundational design assumptions eliminate the need for boilerplate code and account for an easier-to-navigate framework, thereby reducing maintenance complexity and project costs.
Cost Savings. As an Open Source framework, Grails can be broadly adopted and used with no vendor lock-in, contracts, license management, or run-time licensing fees.
0コメント