How to reduce turnaround time in JavaEE application development?

本文共计343个文字，预计阅读时间需要2分钟。

One issue with developing Java EE apps is the lengthy edit-compile-deploy cycle. I attempted to use Jetty, but it still took too long.

OnetroublingaspectofbuildingJavaEEapplicationsistheturnaroundtimefortheedit,compile,

One troubling aspect of building Java EE applications is the turn around time for the edit, compile, deploy process. I tried using Jetty but even that has some problems after making several edits you will usually run into a memory error.

构建Java EE应用程序的一个令人不安的方面是编辑,编译和部署过程的周转时间。我尝试使用Jetty,但即使在进行多次编辑后仍有一些问题,您通常会遇到内存错误。

At the moment I use Netbeans and I can see edits to the presentation layer without redeployment but when making changes to the model then a full rebuild is necessary and there could be some problems.

目前我使用Netbeans并且我可以看到对表示层的编辑而无需重新部署,但是当对模型进行更改时,则需要完全重建并且可能存在一些问题。

What are some recommendations for improving this aspect of the process?

有哪些建议可以改善这一过程?

2 个解决方案

#1

Troubling? Really? How long are your projects?

令人不安?真?你的项目有多长?

I think that Spring dm Server might start making in-roads with its OSGi technology. It keeps deployments modular, and you can hot deploy/undeploy individual modules.

我认为Spring dm Server可能会开始使用其OSGi技术。它使部署模块化,您可以热部署/取消部署单个模块。

#2

You could use JavaRebel

你可以使用JavaRebel