- This topic has 1 reply, 2 voices, and was last updated 19 years, 4 months ago by
.
-
Posts
-
Hello,
I’ve just installed MyEclipse and I try to migrate a big project (> 7000 classes) from JBuilder to Eclipse. The code migration was not a big deal, but what I try to see is how can I use Weblogic 6 with MyEclipse in the same way as I used JBuilder: automatic deployment of all the webapps, debug mode, etc…If MyEclipse can offer us the same features we will not migrate to JBuilder X. But I am not completely convinced about the Weblogic integration part. I have to mention that in out project we have severals webapps, not just one and I would like to keep only one project and not a project per webapp like in your tutorials. Could you please help me with some examples on how to migrate a big project from JBuilder to MyEclipse if this is possible?
Thank you,
Alex.Alex,
If you choose to migrate to MyEclipse the individual web modules or web projects will each need to become a web project in MyEclipse. THe reasons for this pretty much span the scope of development, autocomplete, library resolution, compilation, deployment and debugging.Also for Java class debugging (Servlet, Actions, EJBs, etc.) most application servers will work, as long as you can connect the Remote debugger to them (will be much more streamlined in 3.8.3 release in the next 2 weeks). However for the best debugging AND JSP debugging your application server needs to support JSR 45 (which WL 6 does not IIRC) and you need to be using a 1.4 VM to run Eclipse and the application server.
Reading our tutorials and physically making a copy of your giant project and trying to partition it into MyEclipse Web Projects will be the best way to start and then ask us specific questions. Just make sure that each Web Project resembles a runnable web application; also note that you can adjust the deployment settings for a project if it requires another Java Project for libraries or the like. There are lots of ways to set this up, and in 3.8.3 we are making it even more flexible to allow for even MORE ways to setup projects. But throwing multiple web apps under one Web Project is not supported, nor will it be as our Enterprise Application Project treats these as individual modules for deployment, and we must continue to honor that.
I think once you migrate you might find it much easier than you thought. If not, I suppose the $3970.01 alternative for JBuilder X is always available 😛
Most importantly if you do choose to try and migrate, we would appreciate any feedback and questions kept to this thread so others can help/learn from your experiences as well. We have had and I’m guessing will continue to have many JBuilder converts and the project structure change over is always the biggest pain for people that I can see.
