Grails(6)Guide Book Chapter 7 The Web Layer

Grails(6)Guide Book Chapter 7 The Web Layer
7 The Web Layer
7.1 Controllers
A controller can generate the response directly or delegate to a view.
To create a controller, simply create a class whose name ends with Controller in the grails-app/controllers directory.

The default URL Mapping configuration ensures that the first part of your controller name is mapped to a URI and each action defined within your controller maps to the URIs within the controller name URI.

7.1.1 Understanding Controllers and Actions
Creating a controller
There are 2 commands create-controller and generate-controller
>grails create-controller book
To create a file /grails-app/controllers/myapp/BookController.groovy

Creating Actions
A controller can have multiple public action methods, each one maps to a URI
class BookController {
def list(){
//do controller logic, get a model
return model
}
}
This method will map to the URI /book/list

Public Methods as Actions

The Default Action
The default action of the Controller, for example, if /book is hit, the action that is called when the default URI is requested is dictated by the following rules.
1. If there is only one action, it is the default
2. If you have an action named index, it is the default
3. Alternatively you can set it explicitly with the defaultAction property.
static defaultAction = "list"

7.1.2 Controllers and Scopes
Available Scopes
Scopes are hash-like objects where you can store variables.

servletContext - application scope, instance of SevletContent

session - an instance of HttpSession

request - an instance of HttpServletRequest

params - mutable map of incoming request query string or POST parameters

flash -

Accessing Scopes
class BookController {
def find(){
def findBy = params["findBy"]
def appContext = request["foo"]
def loggedUser = session["logged_user"]
}
}

Or we can visit the parameters like this
def find(){
def findBy = params.findBy
def appContext = request.foo
def loggedUser = session.logged_user
}

Using Flash Scope
Flash scope as a temporary store to make attributes available for this request and the next request only. Afterwards the attributes are cleared.

This is really useful for setting a message directly before redirecting.

def delete(){
def b = Book.get(params.id)
if(!b){
flash.message = "User not found for id ${params.id}"
redirect(action:list)
}
…snip...
}

Scoped Controllers
There are several scopes supported by grails:
prototype (default) - A new controller will be created for each request.
session - One controller is created for the scope of a user session
singleton - Only one instance of the controller ever exists

To configure that in controller
static scope = "singleton"

To configure that for all the controllers in Config.groovy
grails.controllers.defaultScope = "singleton"

7.1.3 Models and Views
Returning the Model
A model is a Map that the view uses when rendering.

def show(){
[book: Book.get(params.id)]
}

class BookController {
List books
List authors
def list(){
books = Book.list()
authors = Author.list()
}
}

These are for default settings, we can use ModelAndView directly.

def index(){
def favoriteBooks = …
return new ModelAndView("/book/list", [bookList: favoriteBooks])
}

One thing to bear in mind is that certain variable names can not be used
attributes, application

Selecting the View
For the show Action,
class BookController {
def show(){
[book: Book.get(params.id)]
}
}
Grails will look for a view at the location grails-app/views/book/show.gsp

If we want to control that, we need to render to a different view, we use render method:
def show(){
def map = [book: Book.get(params.id)]
render(view: "display", model:map) //grails-app/views/book/display.gsp
}

def show(){
def map = [book: Book.get(params.id)]
render(view: "/shared/display", model:map) // grails-app/views/shared/display.gsp
}

Rendering a Response
Render snippets of text or codes to the response directly from the controller.

render "Hello Sillycat!"

render(text:"<xml>Some Xml</xml>", contentType: "text/xml", encoding: "UTF-8")

References:
http://grails.org/doc/latest/guide/index.html
http://grails.org/doc/latest/guide/theWebLayer.html
内容概要:本文详细介绍了“秒杀商城”微服务架构的设计与实战全过程,涵盖系统从需求分析、服务拆分、技术选型到核心功能开发、分布式事务处理、容器化部署及监控链路追踪的完整流程。重点解决了高并发场景下的超卖问题,采用Redis预减库存、消息队列削峰、数据库乐观锁等手段保障数据一致性,并通过Nacos实现服务注册发现与配置管理,利用Seata处理跨服务分布式事务,结合RabbitMQ实现异步下单,提升系统吞吐能力。同时,项目支持Docker Compose快速部署和Kubernetes生产级编排,集成Sleuth+Zipkin链路追踪与Prometheus+Grafana监控体系,构建可观测性强的微服务系统。; 适合人群:具备Java基础和Spring Boot开发经验,熟悉微服务基本概念的中高级研发人员,尤其是希望深入理解高并发系统设计、分布式事务、服务治理等核心技术的开发者;适合工作2-5年、有志于转型微服务或提升架构能力的工程师; 使用场景及目标:①学习如何基于Spring Cloud Alibaba构建完整的微服务项目;②掌握秒杀场景下高并发、超卖控制、异步化、削峰填谷等关键技术方案;③实践分布式事务(Seata)、服务熔断降级、链路追踪、统一配置中心等企业级中间件的应用;④完成从本地开发到容器化部署的全流程落地; 阅读建议:建议按照文档提供的七个阶段循序渐进地动手实践,重点关注秒杀流程设计、服务间通信机制、分布式事务实现和系统性能优化部分,结合代码调试与监控工具深入理解各组件协作原理,真正掌握高并发微服务系统的构建能力。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值