Liferay门户开发官方指南：Liferay In Action

4星 · 超过85%的资源需积分: 10 122 浏览量更新于2024-07-29 收藏 19.15MB PDF 举报

"Liferay In Action 完整版" 《Liferay In Action》是Richard Sezov Jr.撰写的一本关于Liferay Portal开发的官方指南。这本书由Manning出版社出版，并得到了Brian Kim的序言支持。Liferay是一款开源的企业级门户平台，广泛用于构建企业内部或外部的协作和信息共享环境。本书深入探讨了Liferay Portal的各个方面，包括但不限于以下关键知识点： 1. **Liferay Portal概述**：介绍Liferay Portal的基本概念，它的核心功能以及如何为企业提供一个灵活、可扩展的平台来构建和管理Web应用。 2. **安装与配置**：详细讲解如何在不同的操作系统和服务器环境下安装和配置Liferay Portal，包括数据库连接、服务器配置和安全性设置。 3. **主题与布局**：讨论如何自定义Liferay的外观和布局，包括创建和修改主题，以及使用portlet布局来满足不同用户需求。 4. **Portlet开发**：介绍如何使用Java Portlet API和其他相关框架（如Spring和JSF）来开发自定义portlet，以实现特定业务功能。 5. **服务和API**：详细解析Liferay的API和服务，包括服务建模语言（SML）、服务层（Service Layer）和数据访问对象（DAO），以及如何利用这些工具进行模块化开发。 6. **工作流和表单**：讨论Liferay中的工作流引擎和表单构建工具，帮助读者理解如何实现审批流程和数据收集。 7. **社区和社交功能**：阐述Liferay的社区管理特性，如用户组、论坛、博客、日历等，以及如何利用这些功能促进用户互动和协作。 8. **安全性和权限管理**：讲解Liferay的安全模型，包括角色、权限和访问控制，以及如何保护敏感信息和资源。 9. **性能优化**：提供性能调优策略，包括缓存机制、数据库优化和集群配置，以确保Liferay在高负载环境下的稳定运行。 10. **集成与扩展**：探讨与其他系统（如SAP、Salesforce等）的集成，以及如何通过插件和API扩展Liferay的功能。 11. **维护与部署**：指导读者进行版本升级、备份恢复、监控和故障排查，确保Liferay系统的持续运行和维护。 12. **最佳实践**：分享作者和社区的经验，提出开发和管理Liferay项目的最佳实践和建议。本书不仅适合Liferay的新手，也适合有一定经验的开发者，通过丰富的示例和实战指导，帮助读者全面掌握Liferay Portal的开发和管理。对于想要利用Liferay构建高效企业门户或社区网站的人来说，这是一本不可或缺的参考书籍。

preface

I was sitting in the back of the Liferay Car (yes, Liferay owns an old, beat-up Toyota

Corolla), and Brian Kim, Liferay’s Chief Operating Officer, was sitting next to me, giv-

ing me a hard time. I was already uncomfortable in the back seat: I’m 6'2", and my

knees were up next to my ears. But it was only a short trip from the Liferay Symposium

hotel in Anaheim, CA, to Brian Chan’s house (where we and the other occupants of

the car were staying), so I wouldn’t have to endure the cramped quarters for long.

You see, I’d written a couple of editions of Liferay’s Administrator’s Guide, but its

companion volume, the Developer’s Guide, had suffered several aborted attempts at get-

ting off the ground. It had finally achieved some semblance of completion, but it

wasn’t yet where I wanted it to be. The problem was, I needed to release some devel-

oper documentation soon, so I could get to work on the training materials and the

documentation for the next release of Liferay. For this reason, I’d resigned myself to

publishing what we had and then attempting to make the next edition of the book

more complete. We’d been self-publishing the Administrator’s Guide, so I thought we

should do the same with the Developer’s Guide, particularly because it wasn’t going to be

as complete as I wished.

Brian wasn’t giving me a hard time because of that: Liferay was in a period of rapid

growth, and we often found ourselves in the position of having more work than we

had hands to complete it. Instead, Brian was giving me a hard time, frankly, because

he had a bigger vision than I had.

“Why do you want to self-publish again?” Brian asked. “Don’t you think it would be

better if we worked with a book publisher?”

PREFACE

xvi

“Of course it would,” I said. “I just think that the material I currently have isn’t yet

up to the standards that one of the two publishers I’d want to work with would

accept.”

“Really? Okay, what would it take to get it that way?”

“Well, I’d have to be able to dedicate more time to writing the book, which I can’t

do right now.” I then gave him my sob story about all the work that I had to finish in

addition to the Developer’s Guide.

“Then let’s hire some people to help you. One problem solved. Who are the two

publishers you’d like to work with?”

I told him. Manning was one of them. The other shall remain nameless.

“Why do you like those guys?” Brian asked.

My only real experience with computer book publishers—before I wrote this

book—was as a reader. Because I’m mostly self-educated with regard to the industry

I’m in, I’ve read a lot of computer books (my degree is in English; how I got into pro-

gramming, Java, and portals is another—longer—story). I answered from that per-

spective.

“I think the quality from those guys is consistently higher than the rest. And, of

course, I’d want Liferay to be represented by that kind of quality. So I’d want to be

able to take the time to deliver something that they’d be willing to publish.”

“Okay, then why don’t we make it a goal to reach out to those publishers, once we

get you some help? I think working with a publisher will help provide us with more vis-

ibility and fill a real need our community has for some good, polished material to get

them up to speed on Liferay.”

“All right, I can do that,” I replied.

Except I never really got the chance.

By the hand of what can only be described as Providence, not even a month later,

Manning reached out to us. I say us because they didn’t reach out to me; they went after

the Liferay rock stars, like Brian Chan, Nate Cavanaugh, and Ray Augé, which makes

perfect sense. But those guys were far too busy to write a book: if they spent time

doing that, Liferay wouldn’t be where it is today. Instead they sent Manning, specifi-

cally Mike Stephens, to little old me, who was supposed to be preparing a proposal to

send to Manning anyway.

Funny how these things work out, isn’t it?

Through a long, circuitous route that I could never have planned, I get to fulfill a

dream of being a published author. It’s not a novel (that may come someday too, I

hope), but I’ve tried to make what could become a dry subject interesting. To me,

there’s nothing dry about Liferay: it’s an exciting product that can do a ton of things,

and I think it’s an ideal platform on which to build a web site. I hope that by the end

of this book, you’ll think so too.

ACKNOWLEDGMENTS

xviii

the help of several of them, but the man I want to mention first is Ray Augé. Ray is one

of the smartest guys I know, and he’s the mind behind many of Liferay’s most robust

features. He took lots of time out of many of his days to help me puzzle out some

undocumented and tricky (at least to me)

APIs—which are now documented in this

book. He didn’t just do this for me, though—he does this for everybody. I have no

idea how he gets his own work done, because he’s constantly putting himself out for

others, yet he consistently delivers on making Liferay better and better with each ver-

sion. Thanks, Ray, for all of your help with this book.

Jorge Ferrer is another one of these guys who seems to achieve the impossible.

Somehow he manages to run the Liferay office in Spain, drive many of Liferay’s proj-

ects, help other people (like me), contribute to Liferay’s core, and heavily involve

himself in Liferay’s community. Always positive, always energetic—quite frankly some-

times it makes me tired just thinking about all he does. Thanks, Jorge.

Thanks to Mike Young for walking me through Liferay’s page composition logic in

chapter 9. That was fun to puzzle out and added an important aspect to the book. In

many ways I also owe Mike for planting the seeds that got me into Liferay in the first

place. Thanks, Mike!

My graphics skills are somewhat lacking, and I definitely want to thank Emily

Young for her awesome fake product images, and Jon Neal for the graphic design of

the Inkwell theme. Believe me, you wouldn’t have wanted to see the versions I was try-

ing to make.

If you’ve read the preface, you know that we had to hire some help for me in order

to make this book possible. That help came in the form of Stephen Kostas. Steve

picked up many of my responsibilities of keeping Liferay’s training materials up to

date and free from error, making it possible for me to make only quick, sideways

glances at the training material for the last year. Thanks, Steve, for being so easy to

work with and so willing to pick up a wide variety of tasks.

I guess I have to move this along faster, or it’ll get to be as long as the book itself.

Thanks to all the trainers who helped keep the training material going while I was

working on the book: Julio Camarero, Juan Fernandez, Olaf Kock, Jonathon Omahen,

Sten Martinez, Alberto Montero, Zsigmond Rab, and Steven Cao. Thanks to Tim Tel-

cik for taking off and running with the

PDF tools.

Speaking of training, special thanks to Ed Shin and Jeff Handa for helping me

maximize my time on the book by organizing various training tasks. Thanks also to

Mike Han for keeping us in line and for your help with my workflow questions.

Thanks to Greg Amerson for the awesome Liferay

IDE/Developer Studio and all of

your excellent feedback. You’re making Liferay development easier every day, man.

To Ivan Cheung and James Min: I wouldn’t be in Liferay without you guys. Thanks!

Neil Griffin is to me the (slightly) older brother I never had. Thanks for your

encouragement and wisdom, Neil.

Thanks to my many coworkers who were so encouraging over the past year: Josh

Asbury, Alice Cheng, Paul Hinz, James Falkner, Michelle Hoshi, JR Houn, Mike

ACKNOWLEDGMENTS

xix

Saechang, Scott Lee, Nate Cavanaugh, Aaron Delani, Craig Kaneko, Ryan Park, Cyn-

thia Wilburn, Charles May, Zsigmond Rab, Zsolt Balogh, Jeff Young, Ed Chung, Jerry

Niu, Jeff Han, Louis Mui, Juan Fernandez, Thiago Moreira, Ruth Huijser, Joe Shum,

and Alex Chow. Thanks to Cecilia Lam for putting up with my hare-brained sympo-

sium ideas (a compliments contest?) so people could win copies of this book.

Manning put together a fantastic team for this book. Thank you, Marjan Bace, for

such a great bunch of people to work with, and for your hands-on approach. Thanks

to Mike Stephens for getting it all started. Lianna Wlasiuk was my developmental edi-

tor, and I am grateful to you, Lianna, for all you did to make this book better. I

learned a great deal about how to put together a quality book manuscript, and I know

it’s going to spill over into my other work in the future.

Thanks to Karen Tegtmeyer for managing the review process so well, and thank

you to all of my reviewers: Sean Hogg, Armin Dahncke, Davide Piazza, Ashish Sarin,

Barbara Regan, Tariq Ahmed, John J. Ryan III, John Griffin, Robert Hanson, Jakub

Holy, James M. Denmark, Pete Helgren, Manish Gupta, Tomáš Polešovský, Sopan She-

wale, Sumit Pal, and John Stevenson. You made the book stronger by your sugges-

tions. Special thanks to Minhchau Dang for doing a final technical review of the

manuscript shortly before it went to press. Thanks also to Mary Piergies, who shep-

herded the book through production, and to my copyeditor, Tiffany Taylor, and my

proofreader, Melody Dolab.

Of course, I also need to thank my mom, Constance Hunter, for believing I could

write books from the time I started making science fiction stories out of my spelling

sentences in the sixth grade.

Thanks most especially to God for His mercy to me, giving me the strength and

stamina to complete the book.

I hope I haven’t forgotten anybody. If I have, it was unintentional—please accept

my apologies and my sincere thanks.

剩余377页未读，继续阅读

茶尼

粉丝: 8
资源: 11

Liferay门户开发官方指南：Liferay In Action

Liferay Portal开发官方指南：Liferay in Action

Liferay Portal开发官方指南

Liferay 门户开发官方指南：Liferay Portal 开发指南

Liferay in Action完整版

spring in action 2.0

LiferayinAction电子书完整版

LiferayinAction完整版_1

微生物细胞壁中S层蛋白的功能与结构解析及其应用前景

一个简单的Python爬虫示例，使用了requests库来发送HTTP请求，以及BeautifulSoup库来解析HTML页面 这个示例将从一个简单的网页中获取标题并打印出来

深度学习中全连接神经网络与卷积神经网络融合用于猫狗二分类任务（PyTorch实现）-含代码设计和报告

最新资源

一个简单的Python爬虫示例，使用了requests库来发送HTTP请求，以及BeautifulSoup库来解析HTML页面这个示例将从一个简单的网页中获取标题并打印出来