不再使用jsp标准操作了吗？
对于所有在生产环境中编写 jsp 的人来说，这是一个简单的问题。您使用 jsp 标准操作吗？为什么？一些常见的用例可能是什么？
我问这个问题是因为有很多标记库似乎功能更强大，而且我不确定是否值得考虑任何任务的标准操作。
谢谢。
编辑：通过标准操作，我的意思是：
jsp:useBean
jsp:getProperty
jsp:setProperty
jsp:include
jsp:forward
jsp:param
jsp:plugin
jsp:attribute
jsp:body
jsp:element
jsp:text
This is a quick question for all of you writing jsps in production. Do you use jsp standard actions and why? What are maybe some of common use cases?
I ask because there are so many taglibs out there that seem to be so much more capable and I am not sure if considering standard actions for any task is worth is anymore.
Thanks.
Edit: By standard actions I mean the fol:
jsp:useBean
jsp:getProperty
jsp:setProperty
jsp:include
jsp:forward
jsp:param
jsp:plugin
jsp:attribute
jsp:body
jsp:element
jsp:text
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
仍在使用
jsp:include，但不经常使用。自从采用 EL、JSTL 和 Tiles 后，根本没有使用其余的。对于 Tiles，我们不需要使用
jsp:include，但没有理由仅仅为了使用tiles:insert，我倾向于在引用定义时只使用tiles:insert。Still using
jsp:include, but not often. Not used the rest at all since adopting EL, JSTL and Tiles.With Tiles, we don't need to use
jsp:include, but there's no reason to usetiles:insertjust for the sake of it, I tend to only usetiles:insertwhen referencing definitions.只有
一些 JSP 纯粹主义者可能会选择
相关问题：
Only the
<jsp:include>(and<jsp:param>as child) is useful. The remnant is ultimately useless when using a proper MVC design or framework. Maybe the<jsp:plugin>is useful for applets, but since some years there exist an applet deployer JavaScript file which makes it superfluous.Some JSP purists may opt that
<jsp:useBean>is also useful in order to trigger IDE autocompletion of bean properties in EL. But it is not required per se when using the MVC approach.Related questions: