Recently, I read a comment that said J2EE developers use Jboss for development, but other app servers like WebLogic for production, due to the latter many additional features. This got me thinking, since doing that means several things:
1.It implies a migration (deploy descriptors at minimum).
2.Special features in the production are not used (or worse, not tested) in the development one, so production server is not exploited.
3.Potential configuration problems are not found until staging (if it takes place).
I asked around, and found that indeed, there are developers that do that since JBoss small footprint makes them more productive and their machine not so slow.
How many of you do this? If working on JBoss, which development environment do you use? Why use JBoss (or the server you use for development) and why not the others? Is the migration that comes after, impacting in time or resource consuming? Thanks for your feedback on this.
This conversation is currently closed to new comments.
At a former job developing Online Banking for a mid-sized financial institution, we used Tomcat for development on our PCs, then shipped it to a QA server running the Sun ONE Web Server for testing, then from there to a production server also running the Sun web server.
We weren't using EJBs, so Tomcat was sufficient. It worked fine. There were only one or two tiny places where there were any compatability issues.
Dev licenses for WebLogic are costly, so developers may be forced to share a dev server if they request WebLogic for their dev environment when a free servlet container like Tomcat or JBoss is sufficient.
Of course, if that's true, what value is WebLogic providing in your production environment if you can get along without it in your dev environment?
Cost may be one point. But aren't around free development licenses? I'm not sure but at least on Weblogic I think they give away the server and the development with developers license, the cost comes when you use the server for deployment. If you are working for a company that already has Weblogic installed, would you use Jboss to develop and then migrate the result?
JBoss is open source, fully J2EE compatible. Most small to medium sized companies would be using this, rather than pay for the licence fees for Weblogic etc.
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
J2EE development environment preference?
1.It implies a migration (deploy descriptors at minimum).
2.Special features in the production are not used (or worse, not tested) in the development one, so production server is not exploited.
3.Potential configuration problems are not found until staging (if it takes place).
I asked around, and found that indeed, there are developers that do that since JBoss small footprint makes them more productive and their machine not so slow.
How many of you do this? If working on JBoss, which development environment do you use? Why use JBoss (or the server you use for development) and why not the others? Is the migration that comes after, impacting in time or resource consuming?
Thanks for your feedback on this.