这里有人在新项目中使用 Struts 1 吗？
我有一个场景，客户要求在 Struts 1 上开发一个新项目。看起来他们有许多应用程序在 Struts 1 上运行，并且内部 IT 团队对此感到满意。
对于数据访问，我们被要求编写 JDBC，没有 ORM，甚至没有 Spring DAO。 他们开发了一个框架，我们被要求使用它。
我想知道这里是否有人遇到过类似的情况，并设法说服客户使用更新的框架。
I have a scenario where customers are asking to develop a new project on struts 1. It appears they have many applications running on Struts 1 and the in house IT team is comfortable with it.
For data access, we are asked to write JDBC, no ORM, not even Spring DAO. They have developed a framework and we have been asked to use that.
I'm wondering if anyone here have been in a similar situation, and managed to convince the customer to use newer frameworks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我也经历过类似的痛苦场景。 要赢得争论，你首先必须说服他们。
说“Struts 1 糟透了”并不能解决问题，因为他们总是可以说“它已经过测试，并且适用于其他项目”。
我所做的是：
1）我在一个更好的框架中创建了一个原型，我发现该框架适合这项工作（在我的例子中是 Rife）......在 3 天内。
2) 我在 Struts 1.x 中创建了相同的原型...我成功地在 5 天内完成了它，但正如预期的那样，这要痛苦得多。
3) 然后我创建了一个演示文稿，其中包含漂亮的图片、代码指标以及我从 Rife 等框架免费获得的东西，而这些是我从 Struts 1 中得不到的。
最终他们选择了带有 Hibernate 的 Struts 2。 更好，但最终这仍然是一个错误的决定。 我们在 18 个月内交付了我们的应用程序，而我们本来可以在 3 个月内完成。技术选择并不是唯一的罪魁祸首......我们必须遵循各种内部程序，而且我们还必须重写由于我们管理层政策的变化，大部分代码都被修改了，更不用说与各种已弃用的内部系统的集成了。
我得出的唯一结论是，在大商店中开发的企业软件确实会耗尽软件开发人员的生命。
I've lived a similarly painful scenario. To win an argument you first have to convince them.
Saying that "Struts 1 sucks" won't cut it, since they can always say that "it's tested, and it works for the other projects".
What I did is this:
1) I created a prototype in a better framework that I found suited for the job (in my case was Rife) ... in 3 days.
2) I created the same prototype in Struts 1.x ... I managed to do it in 5 days, but it was a lot more painful, as anticipated.
3) I then created a presentation with pretty pictures, code metrics, and things that I get for free from a framework like Rife, that I don't get from Struts 1.
In the end their choice was Struts 2 with Hibernate. Better, but still, it was in the end a bad decision. We delivered our application in 18 months when we could've done it in 3. The technological choice isn't the only one to blame here ... we had all sorts of internal procedures we had to follow, and we also had to rewrite large portions of code because of the shifting policies of our management, not to mention integration with all sorts of deprecated internal systems.
The only conclusion I came to was that enterprise software done in big shops really suck the life out of software developers.
Struts 1 仍然被许多公司使用，因为它是一个蓝图（公司决策），因此他们不能使用其他任何东西。
这是我们必须经历的一个非常常见的场景（我想说的是一个标准场景）。
Struts 1 is still used by many companies because it is a blueprint (a corporate decision) and therefore they cannot use anything else.
This is a very common scenario (I would say a standard scenario) which we have to live.