支持 JSR 286,无需编写 portlet

发布于 2024-09-27 19:22:41 字数 247 浏览 0 评论 0原文

我们收到的要求是我们的新项目必须符合 JSR 286,以便它最终可以托管在 SharePoint 中。但与此同时,我们被告知我们没有被要求编写 portlet。只要符合标准即可。我们最初考虑使用 Struts 2 并编写一个普通的应用程序。

这对任何人都有意义吗?我将开始深入研究该标准,但到目前为止我读过的内容使这看起来不仅仅是“这样做……不要这样做……这样命名”之类的交易。您要么编写 portlet,要么不编写。我错了吗?有谁知道有任何文章会指向任一方向吗?

We've been given a requirement that our new project be JSR 286 compliant so that it can eventually be hosted in SharePoint. But in the same breath we were told that we're not being asked to write a portlet. Just be compliant with the standard. We were originally thinking of using Struts 2 and just writing a normal application.

Does this make sense to anyone? I'm going to start digging through the standard but the stuff I have read so far makes it seem like this isn't just a "do this.. don't do this.. name things this way" kind of deal. You either write a portlet or you don't. Am I wrong? Does anyone know of any articles that would point in either direction?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

清晰传感 2024-10-04 19:22:41

JSR 286 是 Java portlet 2.0 应用程序的规范。据我所知,在 SharePoint 中使用 Java portlet 的唯一标准方法是通过 WSRP,但这是 JSR 286 的一个单独规范。如果您要提供自己的 WSRP 实现,我不知道您为什么要制作符合 JSR 286 应用程序要求。

我想知道他们是否意味着您应该使用预构建的 portlet。例如,如果您使用基于 JSF 的 portlet 应用程序,那么您通常不会创建自己的 portlet,而是依靠预先构建的实现来充当控制器并抽象出一些特定于实现的事物(尽管您仍然必须为 portlet 编写您的视图 - 不包括标头标记等)。

我想要求澄清一下要求。

JSR 286 is the specification for Java portlet 2.0 applications. The only standard way I know of to consume Java portlets in SharePoint is via WSRP, but that is a separate spec to JSR 286. If you were going to provide your own WSRP implementation, I don't know why you would want to make the application JSR 286 compliant.

I wonder if they mean that you should use a pre-built portlet. For example, if you were using a JSF-based portlet application, you would generally not create your own portlet, but rely on a pre-built implementation to act as a controller and abstract away some of the implementation-specific things (though you still have to write your views for a portlet - not including header markup and so on).

I would ask for a clarification of the requirements.

后来的我们 2024-10-04 19:22:41

如果您干净利落地使用 JSF,您就不会遇到运行在 servlet 环境还是 portlet 环境中的问题。只要你不这样做,例如 ServletContext sctx = (ServletContext)FacesContext.getCurrentInstance().getExternalContext().getContext() 之类的事情。

If you use JSF cleanly you are isolated from the question of whether you are running in a servlet environment or a portlet environment. Just as long as you don't do e.g. ServletContext sctx = (ServletContext)FacesContext.getCurrentInstance().getExternalContext().getContext(), that kind of thing.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文