使用Scala构建Web应用：Play 2框架实战

5星 · 超过95%的资源需积分: 9 89 浏览量更新于2024-07-23 收藏 5.64MB PDF 举报

"Manning出版的《Play for Scala》是一本关于使用Scala编程语言开发Web应用程序的专业书籍，由Peter Hilton、Erik Bakker和Francisco Canedo撰写，前言由James Ward撰写。本书全面覆盖了Play 2框架的使用，旨在帮助读者掌握构建现代Web应用的技能。" 在介绍中，我们看到《Play for Scala》是专门针对Play 2框架的，这是一个流行的、用于构建Web应用的开源框架，它基于Scala和Java。Play框架以其敏捷开发和实时反馈特性而闻名，能够使开发者更高效地构建应用程序。Scala是一种强大的多范式编程语言，结合了面向对象和函数式编程的特性，使得代码更加简洁且易于维护。书中可能涵盖了以下关键知识点： 1. **Play 2框架基础**：包括安装配置、项目结构、路由机制、HTTP请求和响应处理等，这些都是构建Web应用的基础。 2. **Scala编程基础**：为不熟悉Scala的读者提供必要的语言知识，如类型系统、模式匹配、 Actors模型和并发处理等。 3. **模板引擎**：Play 2支持使用模板语言来创建动态HTML页面，这将涵盖如何创建和使用模板以及如何与Scala代码交互。 4. **控制器和路由**：讲解如何编写控制器以处理用户请求，并通过路由配置将URL映射到适当的处理函数。 5. **测试驱动开发(TDD)**：Play 2框架鼓励使用TDD方法，书中可能会讲述如何编写单元测试和集成测试，确保代码质量。 6. **实时Web应用**：介绍Play的WebSocket和Comet支持，允许开发者创建能实时更新的用户界面。 7. **依赖注入(DI)**：Play 2支持依赖注入，有助于保持代码解耦，提高可测试性和可维护性。 8. **集成第三方库和服务**：如数据库连接、JSON处理、安全控制、身份验证和授权等，这些都是Web应用中常见的需求。 9. **部署和生产环境**：涵盖如何将应用部署到云服务或服务器，以及性能优化和监控。 10. **最佳实践和案例研究**：书中可能包含实际项目案例，演示如何在真实场景下应用Play 2和Scala。这本书不仅适合初学者，也对有经验的开发者有价值，因为它提供了深入的理解和实用技巧，以利用Scala和Play 2框架的优势。通过阅读此书，读者可以提升自己的Web开发技能，学会如何构建高效、可扩展和易于维护的Web应用程序。

acknowledgments

First of all, we would like to thank the Play community who’ve helped turn Play into what

it is today. Without the hard work from the committers, people writing documentation,

asking and answering questions on the forums, writing modules, and all the application

developers using Play, there wouldn’t have been any point in writing this book.

Second, we’d like to thank all the people at Manning who helped us write this

book. Michael Stephens who approached us to write this book. Bert Bates who taught

us how to write. Karen Miller who was our editor for most of the process. Further-

more, we’d like to thank the production team who did a lot of hard work (including

weekends) to get this book to press, and everyone else at Manning. Without you, this

book wouldn’t have been possible.

We’d like to thank, especially, James Ward for writing a thoughtful foreword, Jorge

Aliss who was particularly helpful when we were writing about SecureSocial, the exter-

nal reviewers—Adam Browning, Andy Hicks, Doug Kirk, Henning Hoefer, Ivo Jerk-

ovic, Jeton Bacaj, Keith Weinberg, Magnus Smith, Nikolaj Lindberg, Pascal Voitot,

Philippe Charrière, Stephen Harrison, Steve Chaloner, Tobias Kaatz, Vladimir Kupt-

cov and William E. Wheeler—and technical proofreader, Thomas Lockney, who

devoted their own time to review our book and make it better, as well as the MEAP sub-

scribers who took the time to let us know about issues on the forum.

Last, but certainly not least, we would like to thank you, the person reading this

book. We wrote this book for you, to help you get the most out of Play. The fact that

you’re reading this means that we didn’t do it for nothing, and we hope this book

helps you to build great and wonderful software. If you do, thank you for that too.

ABOUT THIS BOOK

xvii

more. We expect that the reader has a basic understanding of the web in general and

HTTP and HTML in particular.

This isn’t a book about learning Scala, although we understand that Scala is likely

new to many readers as well. We recommend picking up this book after an introduc-

tion to Scala, or in parallel with an introduction to Scala. Though we stay clear of the

hard parts of Scala, some of the language constructs will likely be hard to grasp for

readers who are entirely unfamiliar with Scala.

This book isn’t the one book about Play that covers everything. Partly, this is

because Play is a new framework and is evolving rapidly. Best practices are often not

worked out yet by the Play community. There’s also a more mundane reason: page

count. The subject of testing, for example, didn’t fit within the page limit for the

book, and rather than doing a very condensed chapter about testing, we chose to

leave it out.

If you’re curious, the short version is that Play is highly testable. This is partly due

to its stateless API and functional style, which make the components easier to test. In

addition, there are built-in testing helpers that let you mock the Play runtime and

check the results of executing controller actions and rendering templates without

using HTTP, plus FluentLenium integration for user-interface level tests.

Rather than trying to cover everything, this book tries to lay a foundation, and we

hope that many more books about Play will be written. There’s much to explore

within Play and on the boundaries between Play and the Scala language.

Roadmap

Chapter 1 introduces the Play framework, its origins, and its key features. We look at how

to get started with Play, and glance over the components of every Play application.

Chapter 2 shows in more detail the components of a Play application and how they

relate to each other. We build a full application with all the layers of a Play application,

with multiple pages, and with validation of user input.

Chapter 3 starts with a dive into the architecture of Play. We show why Play works

so well with the web, and how control flows through your application. We look at how

the models, views, and controllers of an application fit together and how an applica-

tion can be modularized.

Chapter 4 focuses on controllers. Controllers form the boundary between HTTP

and Play. We see how to configure a Play application’s URLs, and how to deal with URL

and query string parameters in a type-safe way. We use Play forms to validate and

retrieve user input from HTML forms, and we learn how to return an HTTP response

to the client.

Chapter 5 shows how a persistence layer fits into a Play application. Anorm is a

data access layer for SQL databases that’s bundled with Play and works with plain SQL.

As a possible alternative, we also introduce Squeryl, which is a data access layer that

uses a Scala domain-specific language to query a database.

ABOUT THIS BOOK

xviii

Chapter 6 shows how Play’s template engine works. It discusses the syntax and how

the template engine works together with Scala. We see how we can make reusable

building blocks with templates and how to compose these reusable blocks to construct

larger templates.

Chapter 7 goes into more detail on the subject of Play forms. Forms are a powerful

way to validate user data, and to map data from incoming HTTP requests to objects in

Scala code. They also work in the other direction: they can present Scala objects to a

user in an HTML form. We also learn how to create forms for complex objects.

Chapter 8 introduces Play’s JSON API in the context of a sample application with a

JavaScript front end that uses the Play application as a web service. Play’s JSON API

assists with converting JSON to Scala objects and generating JSON from Scala objects.

Chapter 9 focuses on Play in a bigger context. We see how we can use existing Play

modules and how to create our own modules and plugins. We glance over the various

ways to deploy an application and how to deal with multiple configurations effectively.

Chapter 10 starts with a description of Play’s web service API and how you can

leverage it to consume the APIs of other web applications. The second part of this

chapter introduces more advanced concepts of Play, such as iteratees, a Play library

that helps you work with streams of data and WebSockets.

Code conventions and downloads

All source code in the book is in a

fixed-width

font

this

, which sets it off from

the surrounding text. This book contains many code listings to explain concepts and

show particular Play APIs. The listings don’t always result in a full application; other

code that’s outside the scope of the chapter is also needed. In many listings, the code

is annotated to point out the key concepts.

The code in this book is for Play versions 2.1.x, which is the most recent version of

Play at the time of printing. If you are using a different version of Play, some of the

code details might be different.

For your convenience, we’ve put up complete example applications for all chap-

ters on GitHub: https://github.com/playforscala/sample-applications. These applica-

tions are available for multiple versions of Play, organized in a branch named to the

Play version. The source code is also available for download from the publisher’s web-

site at www.manning.com/PlayforScala.

The code in these applications isn’t identical to the listings in this book; often

things from multiple listings are merged in the complete application. Some additional

HTML markup, which would obfuscate the main point of a listing in the book, is used

in some places for aesthetic reasons.

Author Online

Purchase of Play for Scala includes free access to a private web forum run by Manning

Publications where you can make comments about the book, ask technical questions,

and receive help from the authors and from other users. To access the forum and

ABOUT THIS BOOK

xix

subscribe to it, point your web browser to www.manning.com/PlayforScala. This page

provides information on how to get on the forum once you’re registered, what kind

of help is available, and the rules of conduct on the forum.

Manning’s commitment to our readers is to provide a venue where a meaningful

dialog between individual readers and between readers and the authors can take

place. It’s not a commitment to any specific amount of participation on the part of the

authors, whose contribution to the forum remains voluntary (and unpaid). We sug-

gest you try asking the authors some challenging questions lest their interest stray!

The Author Online forum and the archives of previous discussions will be accessi-

ble from the publisher’s website as long as the book is in print.

About the authors

PETER HILTON is a senior solution architect and operations director at Lunatech

Research in Rotterdam, the Netherlands. Peter has focused on web application design

and development since 1998, working mostly on Java web frameworks and web-based

collaboration. In recent years, Peter has also applied agile software development pro-

cesses and practices to technical project management. Since 2010, Peter has been a

committer on the Play framework open source project and has presented Play at vari-

ous European developer conferences. Together with colleagues at Lunatech, Peter is

currently using Play to build web applications and web services for enterprise custom-

ers in the Netherlands and France. He’s on Twitter as @PeterHilton.

ERIK BAKKER has been building web applications since 2002 and is currently also

employed by Lunatech Research. He put his first Scala application in production in

early 2010 and has worked with Play 2 since its inception. Erik is a Play module con-

tributor and has presented and blogged about the Play framework and Scala. You can

find him on Twitter as @eamelink.

FRANCISCO JOSÉ CANEDO DOMINGUEZ joined Lunatech Research as a software developer

in 2005. He started his professional career in 1997 and has comfortably worked with

languages as diverse as C, C++, Java, XSLT, JavaScript, HTML, and Bash. He’s been

exploring the power of Scala since 2010. Having had first-hand experience with sev-

eral different web frameworks, Francisco finds Play’s approach to be a breath of fresh

air. He is @fcanedo on Twitter.

剩余329页未读，继续阅读

swsteve

粉丝: 0
资源: 28

使用Scala构建Web应用：Play 2框架实战

Manning - Play for Java 2014

Play for Scala深度解析：聚焦Play 2框架

Play for Scala：探索全栈Web开发的新高度

使用Scala构建高性能Web应用：Play Framework实战

[Scala] Play框架开发(Scala 实现)（英文版电子书）

Reactive Web Applications(Manning,2016)

Manning.Reactive.Web.Applications.2016.6.pdf

Java开发者必读：Play框架2实战指南

Play for Java：探索Play Framework 2.x

Scala版Play框架全览：敏捷Web开发利器

最新资源