After my last post about redeployment-problems with Netbeans 6.0, I got a nice and amazing email from Vince Kraemer (Sun) :
"I recently read your blog entry and decided that I should take another look at this. I think the issue you are running into may be addressed by the changes we made recently". He filed a bug for me ...and solved the problem. You can find the solution in the 6.1 stream.
I tried immediately to deploy some p4j5 samples, and it worked (there are still issues with "Clean And Build"). However the "Undeploy And Deploy" procedure was significantly slower, than in Netbeans 6.0.
The next email from Vince (one day later - at Sunday!!) cleared this issue as well: "You may want to consider using 'Run' instead of 'Undeploy and Deploy' as part of your workflow. The undeploy and deploy action deletes and then recopies the classes and jars into the deployment directory. The run action only copies the changed classes and jars into the deployment directory...."
Indeed using the "Run" action was really fast. The deployment of the RunAndBike application (I will release it next time, the whole source code is already available in p4j5) took only few seconds. Netbeans 6.1 wasn't able to open the JSF-pages in the visual designer (because of binding issues). However I use 6.1 for deployment of the business layer. It works great so far.
Windows users have the following options:
- Disabling the directory deployment in Netbeans 6.0
- Using the Netbeans 6.1 daily builds with the "Run" option for directory deployment.
- Installing another operating system :-).
Web Apps, SPA, PWA with vanilla Java Script (ES 6+), CSS 3 and WebStandards only. As simple as possible, but not simpler. See you at: (Progressive) Web apps, Single Page Apps and WebStandards airhacks workshops at MUC airport, Winter Edition
airhacks.fm the podcast:
Stay in touch: airhacks.news.