grails、drools 和票证/问题跟踪器、iTicket
我需要将票务系统集成到我的 grails Web 应用程序中,以便那些经营小公司的人可以轻松处理客户需求/投诉等,并将其直接与用户联系起来。当我搜索插件或构建的应用程序时,我发现:
- drools 插件,小型票务功能/示例,在出现安装错误后,我找到了
- drools-gorm 插件,然后还简要回顾了
- iTicket,我目前正回避它,因为它包含在内角色管理,但没有提及 Spring Security Core 和 UI,这是我用于角色管理的
- 有关使用 Grails 构建小问题跟踪器的文章
我对票务系统的问题领域知识不多,所以我想知道是否有人曾经走过这条路或了解票务系统领域建模和知识。规则引擎一般可以给出一些注释。例如,灵活的规则引擎对于票务系统非常重要,还是仅适用于较重的应用程序?人们还可以用 grails plus drools 做哪些其他可能有用的事情?或者,相反,保持轻量是最好的,因为这些东西在这个领域往往被证明是非常“定制”的。
感谢您的经验。
谢谢
I need to integrate a ticketing system into my grails Web application, so that those running the small company can easily handle customer needs / complaints, etc., tying that in directly with their users. When I searched for a plugin or built application, I found:
- drools plugin, small ticketing capability/example, which after having an installation bug led me to
- drools-gorm plugin, and then also briefly reviewing
- iTicket, which I'm just currently shying away from because of its inclusion of roles management but no mention of Spring Security Core and UI, which is what I'm using for role management
- article on building a small issue tracker with Grails
I don't have a lot of problem domain knowledge with ticketing systems, and so I'm wondering if someone whose gone down this road before or knows ticketing system domain modelling & rules engines in general can give a few comments. E.g. are flexible rules engines very important for ticketing systems, or is this only for heavier weight applications? What kinds of other general things can one do with grails plus drools, that might be useful? Alternatively, the opposite, is staying light weight best, because these things often turn out to be very "custom" in this arena.
Your experience is appreciated.
Thanks
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论