That seems a pretty typical setup. If you were doing this professionally, the next addition would be version control; Subversion is probably the most common.
Edit: If you're looking at the "free" price point on a Java server, Tomcat and GlassFish are the first three to mind, I think JBoss also offered a free/evaluation copy.
If you want a server you'd be hosting remotely, Java is one of the more expensive languages to host; PHP is probably the least expensive to host, with Apache being the most common server.
更新：在不确切知道您需要在服务器端做什么的情况下，我想说一个值得考虑使用的好技术是 Spring Core（可能还有其他一些 Spring 模块）。 Spring 仍然允许您使用 POJO，但允许您使用依赖注入构建应用程序 - 这确保您的代码是松散耦合的。 Spring 值得学习 - 它促进了良好的编程实践，并且当今许多 Java 应用程序都在使用它。
How will you manage your feature/task assignments? I would recommend Google Code if you don't mind allowing your tasks assignments to be public.
Otherwise JIRA is a good alternative (only $10) that my team has started using recently, though I have mixed thoughts about it. A different team currently administers the install so we haven't been able to customize it to our needs.
As for the technical architecture, I would need to know more about your project to make recommendations. Make sure you think about high level components and requirements before selecting technologies.
UPDATE: Without knowing exactly what you need to do on the server side, I would say a good technology to consider using is Spring Core (and possibly some of the other Spring modules). Spring will still allow you to use POJOs, but allow you to construct your application using dependency injection - which ensures your code is loosely coupled. Spring is worth learning - it promotes good programming practices and is used it many Java apps today.
发布评论
评论（2）
这似乎是一个非常典型的设置。如果您是专业人士，那么下一个添加内容将是版本控制； Subversion 可能是最常见的。
编辑：如果您正在考虑 Java 服务器上的“免费”价格点，Tomcat 和 GlassFish 是最先想到的三个，我认为 JBoss 也提供了免费/评估版。
如果您想要远程托管服务器，Java 是托管成本较高的语言之一； PHP 可能是托管成本最低的，而 Apache 是最常见的服务器。
That seems a pretty typical setup. If you were doing this professionally, the next addition would be version control; Subversion is probably the most common.
Edit: If you're looking at the "free" price point on a Java server, Tomcat and GlassFish are the first three to mind, I think JBoss also offered a free/evaluation copy.
If you want a server you'd be hosting remotely, Java is one of the more expensive languages to host; PHP is probably the least expensive to host, with Apache being the most common server.
您将如何管理您的功能/任务分配？如果您不介意公开您的任务分配，我建议您使用 Google 代码。
否则 JIRA 是一个很好的替代方案（只需 10 美元），我的团队最近开始使用，尽管我对此有复杂的想法。目前由不同的团队管理安装，因此我们无法根据我们的需求对其进行自定义。
至于技术架构，我需要更多地了解你的项目才能提出建议。在选择技术之前，请确保考虑高级组件和要求。
更新：在不确切知道您需要在服务器端做什么的情况下，我想说一个值得考虑使用的好技术是 Spring Core（可能还有其他一些 Spring 模块）。 Spring 仍然允许您使用 POJO，但允许您使用依赖注入构建应用程序 - 这确保您的代码是松散耦合的。 Spring 值得学习 - 它促进了良好的编程实践，并且当今许多 Java 应用程序都在使用它。
How will you manage your feature/task assignments? I would recommend Google Code if you don't mind allowing your tasks assignments to be public.
Otherwise JIRA is a good alternative (only $10) that my team has started using recently, though I have mixed thoughts about it. A different team currently administers the install so we haven't been able to customize it to our needs.
As for the technical architecture, I would need to know more about your project to make recommendations. Make sure you think about high level components and requirements before selecting technologies.
UPDATE: Without knowing exactly what you need to do on the server side, I would say a good technology to consider using is Spring Core (and possibly some of the other Spring modules). Spring will still allow you to use POJOs, but allow you to construct your application using dependency injection - which ensures your code is loosely coupled. Spring is worth learning - it promotes good programming practices and is used it many Java apps today.