使用什么框架来引导我的第一个生产scala项目? [英] What frameworks to use to bootstrap my first production scala project?

问题描述

我正在首次涉足量产应用程序的scala. 该应用程序当前打包为战争文件. 我的计划是创建一个由scala编译的工件组成的jar文件，并将其添加到war文件的lib文件夹中. 我的增强功能是通过Jersey&公开的mysql支持的应用程序将通过HttpClient调用与第3方网站集成.我知道如何通过纯Java做到这一点.但是在scala中进行操作时，有几个决策要注意.

I am making my first foray into scala for a production app. The app is currently packaged as a war file. My plan is to create a jar file of the scala compiled artifacts and add that into the lib folder for the war file. My enhancement is a mysql-backed app exposed via Jersey & will be integrated with a 3rd party site via HttpClient invocations. I know how to do this via plain java. But when doing it in scala, there are several decision points that I am pussyfooting on.

1. scala 2.7.7或2.8 RC吗?
通过 querulous的
2. JDBC 该API是否已准备好投入生产?
3. sbt vs maven.我对Maven感到满意.
4. 是否有HttpClient的scala惯用包装器(或者应该像在Java中那样使用它)?

1. scala 2.7.7 or 2.8 RC ?
2. JDBC via querulous Is this API ready for production ?
3. sbt vs maven. I am comfortable with maven.
4. Is there a scala idiomatic wrapper for HttpClient (or should I use it just like in java) ?

我很想听听您关于Scala入门的评论和经验.

I'd love to hear your comments and experiences on starting out with scala.

推荐答案

1. 我将使用2.8.0. 2.8中有太多有用的功能.此外，2.8即将发布最终版本.如果您只是刚开始，为什么不开始呢? FWIW，自Beta1以来，我一直在每天使用的各种工具和库中使用2.8.0.尽管存在错误，但是它们还不足以使我跌至2.7.7.不过，YMMV.
2. 这不会使您的决定变得容易，但是还有其他访问数据库的可能性.例如，我一直在使用 SQueryL ；我喜欢. ORBroker 是另一种选择.
3. 如果您对Maven感到满意，那么请务必使用它.就个人而言，我更喜欢SBT.当我需要实现特殊的构建逻辑时，我可以获得真正的编程语言的全部功能.同样有用，我不必处理XML配置文件. (XML很适合用于数据，但是对于人工编辑的配置文件而言，它是一种糟糕的格式.)
4. 您可以尝试Databinder调度.请参阅这篇文章以获得很好的概述.

1. I would use 2.8.0. There are just too many useful features in 2.8. Besides, 2.8 is closing in on a final release. If you're just starting out, why not start out with that? FWIW, I've been using 2.8.0 since Beta1, in various tools and libraries that I use daily. While there have been bugs, they haven't been enough to make me fall back to 2.7.7. YMMV, though.
2. This isn't going to make your decision any easier, but there are other possibilities for database access. I've been using SQueryL, for instance; I like it. ORBroker is another option.
3. If you're comfortable with Maven, then use it, by all means. Personally, I prefer SBT. I get the full power of a real programming language, when I need to implement special build logic. Just as useful, I don't have to deal with XML configuration files. (XML is good for data, but it's a crappy format for a human-edited configuration file.)
4. You might try Databinder Dispatch. See this article for a nice overview.

这篇关于使用什么框架来引导我的第一个生产scala项目?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！