- This topic has 1 reply, 2 voices, and was last updated 18 years, 5 months ago by
.
-
Posts
-
I am just getting started with web application development using MyEclipse 5.0 and JBoss 4.0. I have a few questions concerning Web Deployment strategies.
-Is it considered better practice to deploy dependant jars for each project or to deploy dependent jars only once in the application server. For instance, nearly every project uses the log4j.jar. Is it better to have each project use its own copy deployed in the WEB-INF/lib directory, or would it be better to deploy the log4j.jar to the server in the server lib for all projects to share?
-What is the difference between a MyEclipse web project and the base Eclipse Web Project? Shouldn’t they be the same thing?
The problem I am having is that I want to use the Crystal Report plugin with MyEclipse. The Crystal Report Project is classified as a Web Project, but I cannot deploy it until I choose to Add Webproject capabilities from the MyEclipse menu. When you do this what does MyEclipse do the project (other than add the J2EE library to the build path) that enables it as a “MyEclipse” Web Project?
-Is there any harm in bypassing the MyEclipse project deployment tools and simply use the server view to deploy Web Projects?
-Is it considered better practice to deploy dependant jars for each project or to deploy dependent jars only once in the application server. For instance, nearly every project uses the log4j.jar. Is it better to have each project use its own copy deployed in the WEB-INF/lib directory, or would it be better to deploy the log4j.jar to the server in the server lib for all projects to share?
Good question, it’s up to you. I tend to like to deploy all my libraries with each project so my projects are completely portable (meaning I can take them and drop them in another server and have them just work). Otherwise you rely on the server being setup a particular way.
-What is the difference between a MyEclipse web project and the base Eclipse Web Project? Shouldn’t they be the same thing?
Historical differences. You normally don’t see this because we disable some of the WTP functoinality when we ship MyEclipse to avoid the cross-polination. But if you installed WTP yourself, you will see overlap quite a bit. We were hoping to merge our project structure ontop of WTP 1.5 but it isn’t quite there yet (flexible enough, smooth workflow, etc.) but is getting there quickly. We will likely merge our project structures for the WTP 2.0 release (Europa) down the road.
The problem I am having is that I want to use the Crystal Report plugin with MyEclipse. The Crystal Report Project is classified as a Web Project, but I cannot deploy it until I choose to Add Webproject capabilities from the MyEclipse menu. When you do this what does MyEclipse do the project (other than add the J2EE library to the build path) that enables it as a “MyEclipse” Web Project?
The key is the nature that is added to your .project file in the root of your project.
-Is there any harm in bypassing the MyEclipse project deployment tools and simply use the server view to deploy Web Projects?
No nothing, that is exactly why we added the server view in the new release, to make management easier/faster.
