Spring MVC开发流程-最佳实践
当我们不考虑服务/DAO 层时，使用 JSP 作为视图层的 Spring MVC / portlet-MVC 应用程序的正确开发过程是什么 - 通常已经完成了。
我的意思是，如果我一次创建控制器 + JSP，我会在一段时间里有点迷失，一切看起来都一团糟，我失去了关于应用程序设计和需求的整体调查。但另一方面，我无法想象我会首先创建 JSP，然后创建控制器，或者首先创建控制器，然后创建 JSP。
Portlet 编程要复杂得多，解决这个问题似乎很重要。
注意：考虑没有开发团队（图形设计师+程序员），我都是自己做的......
What is the right development process of Spring MVC / portlet-MVC application using JSPs as a view layer, when we don't take service/DAO layer in account - it is usually done already.
I mean, if I'm creating controller + JSP(s) at a time, I'm getting kinda lost in a while and everything seems a mess, I'm loosing the overall survey about the application design and requirements. But on the other way I can't imagine that I would create JSPs at first and then controllers or controllers at first and then JSPs.
Programming portlets is much more complicated and having this resolved seems important.
Note: Consider no development team (graphic designer + programmer), I'm doing all by myself...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我首先从技术和“业务逻辑”的角度声明我即将开发的整个 portlet 插件中最重要的区域。我通常为每个这样的区域分配一个控制器。
我喜欢迭代式的编程风格。创建可以通过其货币化的“骨架”。然后我花了两倍的时间让它变得更漂亮。
I start by declaring the most significant areas, within the entire portlet plugin I'm about to develop, from both technology and "business logic" point of view. I usually assign one controller for each such area.
I like the iterative style of programming. Create the "skeleton" that it is acceptable to monetize it. And then I spend 2 times more time by making it fancier.