- This topic has 3 replies, 2 voices, and was last updated 15 years, 5 months ago by support-eugene.
-
AuthorPosts
-
angryYarnMemberAfter creating a workspace in a normal way in MyEclipse Blue, (Import … Existing projects into workspace), deployment fails:
WASX7280E: An application with name “WMS” does not exist.This is a large application that consists of about 7,000 files/155MB in an Enterprise Project, 2 Web projects, 1 EJB project, several dependent projects, and 3rd party jars. I have created dozens of workspace variations attempting to solve this. Two of the workspaces are able to deploy correctly:
1. Create projects from scratch and add code.
2. Import projects, remove files until the projects are almost empty, deployments begins to work, then add all of the files back in.
Neither of these solutions is workable for developers, who will be downloading projects from source control, and then using “Import … Existing projects into workspace”.Things I have tried:
Make files writable.
Edit important files to “tickle” them.
Copied all files from a workspace that deploys correctly.
Variations on EAR, Web, and EJB deployment options.One difference I noticed between good and bad workspaces in the deployment log, as that a good workspace will say:
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable:
“[C:\Program Files\IBM\WebSphere61\AppServer\profiles\WMS_DC\installableApps\WMS.ear, STLABITLAP273Node02Cell, STLABITLAP273Node02, server1, WMS, {{“WMSLoggerConfigWeb.war” “WMSLoggerConfigWeb.war,WEB-INF/web.xml” default_host} {“WMSWeb.war” “WMSWeb.war,WEB-INF/web.xml” default_host}}, {{“null” “WMSLoggerConfigWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1} {“null” “WMSWeb.war,WEB-INF/ibm-web-ext.xmi”AppDeploymentOption.Yes 1}}, false, true, true, C:/Program Files/MyEclipse 6.5 Blue/myeclipse/eclipse/plugins/com.genuitec.eclipse.blue.websphere_6.5.0.zmyeclipse650200806/scriptutil/scriptutil.jar, C:/Program Files/IBM/WebSphere61/AppServer/profiles/WMS_DC/installedApps/STLABITLAP273Node02Cell/WMS.ear/WMSEJB.jar]”… whereas the bad workspace log just shows the enterprise project:
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable:
“[WMS]”Thanks,
Phil.
support-eugeneMemberCan’t reproduce. I have following questions:
1. What websphere version are you deploying to? Are you using local or remote server?
2. “remove files until the projects are almost empty,” – can you say what files you were removing? Were you removing some files from META-INF folder?We would be extremely grateful if you could create some shorter version of the projects that let to reproduce the issue. Problem is likely in some metafiles – either j2ee (web.xml, MANIFEST.MF, application.xml), Websphere-specific (there are some xmi files) or MyEclipse (.project, .settings/*) – so we don’t need any important project artifacts like Java, JSP, HTML, etc.
angryYarnMember1. WebSphere 6.1.0.17, local server.
2. Removed java, javascript, html files etc. Kept critical files such .project, .classpath, web.xml. manifest, application.xmlDeploying exploded from MyEclipse Blue.
Version: 6.5.0 Blue GA
Build id: 6.5.0-Blue-GA-20080609I will create a shorter version that reproduces the issue.
Thanks,
Phil.
support-eugeneMemberPhil,
Thank you in advance. Please send it to support@genuitec.com with topic Attn: Eugene. -
AuthorPosts