DWR 和 WebSphere Commerce - 这是一个很好的组合吗？
我当前的任务是将使用 DWR 实现 AJAX 功能的 J2EE 应用程序 (JDK5) 迁移到 WebSphere Commerce 平台（J2EE 1.4、JDK1.4）。在WebSphere Commerce 中，其想法是让AJAX 调用在Commerce 平台中编写的命令。 WebSphere Commerce 有自己的 AJAX 方法（由 Dojo 提供支持），但我希望能够避免学习曲线并利用 DWR 上的现有知识。
不知道是否有人尝试过在WebSphere Commerce 中使用DWR？
有什么建议（关于 DWR 和 WebSphere Commerce）可以帮助我开始吗？或者...学习 WebSphere Commerce AJAX 方法更好吗？
---- 如果需要通过评论进行更多说明，请提出建议。多谢。
My current task is to migrate a J2EE application (JDK5) that is using DWR for its AJAX capability, into WebSphere Commerce platform (J2EE 1.4, JDK1.4). In the WebSphere Commerce, the idea is for the AJAX to call commands those are written in Commerce platform. WebSphere Commerce has its own AJAX approach (powered by Dojo), but I am hoping I could avoid the learning curve and leverage existing knowledge on DWR.
I wonder if anyone has tried using DWR in WebSphere Commerce?
Any advice (re DWR & WebSphere Commerce), to get me started? or... is it better to learn WebSphere Commerce AJAX approach?
---- Please advice if more clarification is required via comments. Thanks a lot.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我还没有尝试过 DWR，但在 Websphere Commerce 上使用过 DOJO 和 jQuery。 IMO，您使用哪个 JavaScript 库并不重要，因为它可以通过任何方式调用底层 Websphere Commerce 命令...既然您已经熟悉 DWR，我建议您使用它，而不是使用 DOJO，我觉得 DOJO 很麻烦与 jQuery 相比。
I haven't tried DWR yet but have used DOJO and jQuery both and on Websphere Commerce. IMO it doesn't matter which JavaScript library you use since it is any way going to call underlying Websphere Commerce Commands... Since you are already familiar with DWR I would suggest you to go with that instead of using DOJO which I feel is cumbersome compared to jQuery.
与 WebSphere Commerce 的许多方面一样，坚持使用 OOB Dojo 实现的主要（/唯一）原因是 IBM 销售团队。
如果你偏离了 IBM 的指导方针，你的 CEO 会去参加一些商业开放日，看到一些奇特的 3D 动画购物篮，然后决定他必须花一些可耻的钱来购买最新的功能包，而你将成为一个可怜的笨蛋，解释说他刚刚花钱买的奇特的 3D 动画购物篮不起作用，因为它与某某页面上的 jQuery 操作相冲突等等。
我觉得在技术网站上提供政治答案很肮脏。也许我已经转向了黑暗面……但我也曾加入过一些团队，他们放弃了 Dojo，转而使用（当时）精简得多的 jQuery 库，并目睹了后来政治大屠杀的展开……
As with many aspects of WebSphere Commerce, the main (/only) reason to stick with their OOB Dojo implementation turns out to be the IBM sales team.
If you stray outside the IBM guidelines your CEO will go to some Commerce open day and see some whizzy 3D animated shopping basket and decide that he must spend some obscene sum of money to buy the latest featurepack and you'll be the poor sap who has to explain that the whizzy 3D animated shopping basket that he's just forked out for won't work because it conflicts with the jQuery actions on such-and-such page etc. etc.
I feel dirty offering the political answer on a technical site. Perhaps I have been turned to the dark side... But I've also been on teams that have ditched Dojo for the (at the time) far leaner jQuery libraries and watched the political carnage unfold later...