[nicky.jha]

Hi
we are migrating from WSAD5.1 to myEclipse5.0.I have configured WAS5.1 with myEclipse.now i want to import all the source code (without making code changes) from WSAD to myEclipse.now this source contains WSAD specific .project and .metadata file.what to do for that.please help if any one has solution.

Regards
Nicky

[Riyad Kalla]

Nicky,
The easiest thing would be to create comparable MyEclipse projects (Java, Web, EJB, EAR, etc.) and drag and drop the resources from the old projects into the new one.

Additionally you could *try* importing the projects directly into MyEclipse, then using the “Add Capabilities” features to add the correct capabilities to each project to make sure MyEclipse understands the technologies used in each one (e.g. Web, JSF, Spring, Hibernate, JPA, etc.)

[nicky.jha]

Thanks….I have imported ear of my project,but myEclipse overrides .classpath file of project and thats problem because its big project and i cant set manually.

[nicky.jha]

hi…
adding to query above I have configured WAS5.1 with MyEclipse.Now when i do run on server for any project(ear) only option of websphere6.0 is shown .so how to deploy

[nicky.jha]

In WSAD ear is created in different way ie it has one module screen in which all modules and utility jars are added and source screen shows application.xml.when we import our project whole structuring of this ear changes, it creats subfoldes like EarContents etc so what needs to be done.should we create fresh ear (which could be deployed)in Myeclipse…would all the previous modules jars(ejbs) would have WSAD dependency.how to get over this problem.

[nicky.jha]

adding to above for porting EJBs from WSAD to MyEclipse can XDOClet help this ….lot many queries for now….waiting for reply.

Nicky

[Riyad Kalla]

Nicky,
The first problem here is that it sounds like you have WTP installed along side MyEclipse and are confusing the projects and functionalities between the two plugins.

For example, MyEclipse doesn’t create the “EarContents” or “WebContents” folders, WTP does. Also the “Run on Server” command is from WTP, not MyEclipse.

I would suggest you start with a clean install of MyEclipse and port your projects over one at a time to the MyEclipse project structures. Continuing with your current setup can only lead to confusion as you continually try and figure out which plugin provides the functions you are using.

Or if WTP makes more sense for you, using that is fine to, although I cannot provide support for you for WTP (I’m not familiar with it).

[nicky.jha]

thanks….but actually to import EAR i had to open in J2EE perspective of MyEclipse which prompts with dialog that this action requires enablement of WTP extras(that may be the reason of WTP stuff). now how to import ears in MyEclipse?

[nicky.jha]

Now i have imported ear using import archive of MyEclipse(*.* extension).but that is little use to us.one simle question remains is how to import project from WSAD to MyEclipse.one approach which i tried was checking out all the code from CVS in MyEclipse but all the .project and .classpath (which are WSAD specific) come with it so how to overcome.another approach as suggested by you i created new project in Myeclipse and drag and drop but it breaks the package structure into folder(for eg com.trial.practice into com/’trial/practice(folder form))so how to get over this.another approached which i tried was i created new projects(so now it has .project and .classpath of MyEclipse) and in its workspace i copied all the other file/folder(except .classpath and .project) from WSAD.then i refreshed in MyEclipse ide.but now i have to manually put all the classpath entry(after putting it again it breaks int0 folder structure).i also have to set all the project refrences and buildpath entry.our project has 100+ project s which refer each other(project refernces and build path are concerns).so how to do it manually.am i going right?please suggest me the right approach.waiting for reply.

[Riyad Kalla]

Nicky,
I didn’t realize you were needing convert *so* many projects… that could truly become a headache. Let me give you some back-story on our project structure really quickly to better understand how they work:

• Enterprise Application Project – This project is a meta-project. It is not meant to have any source code in it, but rather you use it to specify the “module projects” that belong to it. Then when you deploy this project, MyEclipse packages the Java, Web and EJB Projects you are referencing and deploys them appropriately for you as modules of your EAR.
• Web Project – This project represents a web project or web module. It is laid out in a standard “Exploded WAR” format where the source file exists off the root of the project, along with a WebRoot directory that represents the root of your deployed web project.
• EJB Project – This project represents 1 or more EJBs.
• Java Project – This project represents common code that may be shared among many modules in an Enterprise Application Project. Besides being added to the build-paths of the projects that need it, you can mark any global project as a dependency of the EAR project itself, and it will be packaged and deployed along with the rest of the modules.

Given that description you can see if you have a single EAR project in WSAD that contains code and EJB/WEb modules, you will need to actually break them into their individual modules in MyEclipse.

Note: We are actually working on WSAD project importers but they are not in the product yet, you might want to wait until we get this work done to improve your experience with MyEclipse. The importers should be available in our November release of MyEclipse 6.1

I’m sorry I don’t have better news for you, but converting 100 projects is no small feat and I’d like it to be dead-easy for you if possible.

[Author]

Posts