jetspeed 2 和 pluto 有什么区别？
我正在考虑使用 portlet 将我们的内部应用程序之一实现为门户，因为它具有许多功能，但并非所有用户都需要所有功能。
我查看了 Apache protals 站点，发现有两个项目 - Jetspeed 2 和 冥王星。
尽管 Jetspeed 被描述为门户，Pluto 被描述为 portlet 容器，但它也提供了自己的门户。它们之间及其功能的真正区别是什么？你能推荐我应该开始“玩”哪个吗？
I'm looking into implementing one of our internal applications as a portal using portlets, as it has many functionalities and not all of them are required by all users.
I've looking at the Apache protals site and I saw that there are two projects - Jetspeed 2 and Pluto.
Although Jetspeed is described as portal and Pluto as a portlet container, it also provides a portal of its own. What is the real difference between them and their functionalities? Can you recommend which should I start "playing" with?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Jetspeed 2 使用 Pluto 作为其 portlet 容器，但它旨在成为一个功能齐全的企业应用程序，包括它自己的 portlet 套件、SSO、可定制的安全性、主题等...
如果您希望开始使用门户/portlet ，Jetspeed 2 项目进展迅速，我建议加入邮件列表，因为它们非常有帮助。另外，使用 apache 门户网站上的教程从源代码下载并构建门户，您应该立即启动并运行自定义门户。
Jetspeed 2 uses Pluto as its portlet container, but it is geared towards being a fully functional enterprise application, including its own suite of portlets, SSO, customizable security, themes etc....
If you are looking to get started with portals/portlets, the Jetspeed 2 project is moving along rapidly, and I would suggest joining the mailing lists, as they can be incredibly helpful. Also, download and build the portal from source using the tutorial on the apache portals site and you should be up and running with a custom portal in no time.
我广泛使用 Jetspeed 1。自 J2 和 JSR 186 以来，我一直有点不了解，但这是我的最佳猜测。这只是一个猜测，但我有足够的信心将其发布在这里。
（假设：门户使用 portlet 容器，而 portlet 容器本身无法真正运行。）
Jetspeed 2 的目标是成为一个完整的企业门户，它使用 Pluto 作为 portlet 容器。 Pluto 有自己的简单门户，因为它不希望依赖于任何给定的门户项目。我相信 Pluto 门户并不是企业级的。
Pluto 常见问题解答的这一部分支持上述声明（来自此处） :
I have worked extensively with Jetspeed 1. I have been a bit out of the loop since J2 and JSR 186, but here is my best guess. It is only a guess, but I'm confident enough to post it here.
(Assumption: a portal uses a portlet container, and a portlet container cannot really run by itself.)
Jetspeed 2 aims to be a full enterprise portal which uses Pluto as the portlet container. Pluto has its own simple portal, as it does not want a dependency on any given portal project. I believe the Pluto portal is not intended as enterprise-level.
The statement above is supported by this part of the Pluto FAQ (from here):
Pluto 确实无意用作企业门户。它对于开发很有用（它很小而且速度很快），如果您想开发自己的门户服务器，您可以嵌入它。但这是一项繁重的工作。
如果您想“深入了解”，请查看 JetSpeed。或者我可以推荐你看看 Liferay Portal。它也是开源的，并且带有许多开箱即用的插件（portlet）。因此，它可以让您快速了解可以用它做什么。
Pluto is really not intended to be use as Enterprise Portal. It's useful for development(it's tiny&fast) and you can embed it if you want to develop you own Portal server. But that's a lot of work.
If you want to just "dive in" look at JetSpeed. Or I can recommend you to have a look at Liferay Portal. It's open source as well and it's going with a lot of plugins(portlets) right out-of-the-box. So it gives you a quick impression what is possible to do with it.